APRS Packet Errors for Churanov (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
20260208131827	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Churanov 081300z4904.09N/01336.89E_320/002g...t034h93>1/0 SHSN 1/002 6/005CU 20km (SYNOP)
20260208141726	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Churanov 081400z4904.09N/01336.89E_020/005g...t034h93>1/0 SHSN 7/003CU 3500 (SYNOP)
20260208151743	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Churanov 081500z4904.09N/01336.89E_030/005g...t032h00>0/-0 SHGS VER VIS 002 <50 (SYNOP)
20260208161943	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Churanov 081600z4904.09N/01336.89E_050/007g...t032h99>-0/-0 FG VER VIS 002 100 A (SYNOP)
20260208171742	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Churanov 081700z4904.09N/01336.89E_040/007g...t032h92>-0/-1 SHRA VER VIS 002 100 A (SYNOP)
20260208181815	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Churanov 081800z4904.09N/01336.89E_050/005g...t032h92>-0/-1 SN VER VIS 002 100 (SYNOP)