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
20250121065120K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250121072122K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250121075122K4HCK>APX220,NT4UX-2*,WIDE2-1,qAR,N5AAA-1:=0000.00N/00000.00Wx
20250121082123K4HCK>APX220,WIDE2-2,qAR,W4CAT-1:=0000.00N/00000.00Wx
20250121092125K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250121095126K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250121105128K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250121112129K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250121115130K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250121122131K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx