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
20250316223312K4HCK>APX220,W4GGM-1*,WIDE2-1,qAR,N8DEU-7:=0000.00N/00000.00Wx
20250316230312K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250316233313K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250317000315K4HCK>APX220,NT4UX-2*,WIDE2-1,qAR,W4CAT-1:=0000.00N/00000.00Wx
20250317003317K4HCK>APX220,W4DMM-3*,WIDE2-1,qAR,N4CKV-1:=0000.00N/00000.00Wx
20250317010316K4HCK>APX220,NT4UX-2*,WIDE2-1,qAR,KM4BJZ-1:=0000.00N/00000.00Wx
20250317013320K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250317020318K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250317023319K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250317030321K4HCK>APX220,TCPIP*,qAC,T2BC:=0000.00N/00000.00Wx
20250317033322K4HCK>APX220,NT4UX-2*,WIDE2-1,qAR,KM4BJZ-1:=0000.00N/00000.00Wx