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
20260209102543	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 091000z4925.55N/01724.28E_080/005g...t032h92>0/-1 BR 5/008 8/012 6km (SYNOP)
20260209112229	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 091100z4925.55N/01724.28E_090/005g...t032h92>-0/-1 BR 5/004 8/010 3000 (SYNOP)
20260209122243	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 091200z4925.55N/01724.28E_100/002g...t032h92>0/-1 DZ 8/003 2000 (SYNOP)
20260209132429	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 091300z4925.55N/01724.28E_100/002g...t032h92>0/-1 DZ 8/004 3000 (SYNOP)
20260209142300	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 091400z4925.55N/01724.28E_100/002g...t032h92>-0/-1 SN 8/005 2000 (SYNOP)
20260209152300	OK1COM-10>APZM4A,TCPIP,qAC,T2CZECH:;LKPO 091500z4925.55N/01724.28E_150/002g...t032h92>-0/-1 SN 8/005 2000 (SYNOP)