APRS Packet Errors for LKPO (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
20260208132340	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 081300z4925.55N/01724.28E_090/002g...t039h86>4/2 RA 5/005 8/010 4500 (SYNOP)
20260208142239	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 081400z4925.55N/01724.28E_080/002g...t039h86>4/2 RA 5/006 8/010 6km (SYNOP)
20260208152257	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 081500z4925.55N/01724.28E_070/005g...t037h93>3/2 RA 8/009 8km (SYNOP)
20260208162456	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 081600z4925.55N/01724.28E_090/007g...t037h86>3/1 RERA 8/011 10km (SYNOP)
20260208172256	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 081700z4925.55N/01724.28E_070/005g...t036h86>2/0 4/013 8/016 10km (SYNOP)
20260208182313	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 081800z4925.55N/01724.28E_020/002g...t036h86>2/0 8/019 10km (SYNOP)