APRS Packet Errors for K4HCK (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20250325000938K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250325001239K4HCK>APX220,WIDE2-2,qAR,KM4ACK-2:=0000.00N/00000.00Wx
20250325003939K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250325010940K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250325013942K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250325020942K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250325023943K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250325030945K4HCK>APX220,NT4UX-2*,WIDE2-1,qAR,KM4BJZ-1:=0000.00N/00000.00Wx
20250325033945K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250325040946K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250325043947K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250325050949K4HCK>APX220,W4GGM-1*,WIDE2-1,qAR,N8DEU-7:=0000.00N/00000.00Wx
20250325053949K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx