APRS Packet Errors for GrArber (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
20260208131816	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;GrArber 081300z4906.83N/01308.12E_110/005g...t030h92>-1/-2 REDZ 3/003 4/007 68km A (SYNOP)
20260208141710	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;GrArber 081400z4906.83N/01308.12E_030/002g...t030h99>-1/-1 SN 7/<001 7/008 400 A (SYNOP)
20260208151711	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;GrArber 081500z4906.83N/01308.12E_060/003g...t030h99>-1/-1 FZFG 8/<001 100 A (SYNOP)
20260208161926	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;GrArber 081600z4906.83N/01308.12E_050/003g...t030h92>-1/-2 UP 8/<001 50 A (SYNOP)
20260208171709	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;GrArber 081700z4906.83N/01308.12E_050/007g...t028h99>-2/-2 FZFG 8/<001 50 A (SYNOP)
20260208181726	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;GrArber 081800z4906.83N/01308.12E_070/006g...t028h99>-2/-2 FZFG 8/<001 50 A (SYNOP)