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
20250211081332K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250211084339K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250211091334K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250211094335K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250211101337K4HCK>APX220,W4GGM-1*,WIDE2-1,qAR,N5AAA-1:=0000.00N/00000.00Wx
20250211104337K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250211111338K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250211114339K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250211121340K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250211124341K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250211131342K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250211134344K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx