APRS Packet Errors for Dukovany (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
20260209122209	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Dukovany 091200z4905.72N/01608.07E_060/007g...t036h86>2/0 BR 8/005 6km (SYNOP)
20260209132355	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Dukovany 091300z4905.72N/01608.07E_070/005g...t034h93>1/0 BR 8/003 4000 (SYNOP)
20260209142225	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Dukovany 091400z4905.72N/01608.07E_080/007g...t034h93>1/0 BR 8/003 3000 (SYNOP)
20260209152225	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Dukovany 091500z4905.72N/01608.07E_060/009g...t034h93>1/0 BR 8/003 1000 (SYNOP)
20260209162454	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Dukovany 091600z4905.72N/01608.07E_060/009g...t034h93>1/0 BR 8/003 2000 (SYNOP)
20260209172226	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;Dukovany 091700z4905.72N/01608.07E_070/007g...t034h93>1/0 RA 8/003 1000 (SYNOP)