APRS Packet Errors for OK0X-10 (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
20260208133003OK0X-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L5128Rn
20260208135003OK0X-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L5128Rn
20260208141004OK0X-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L5128Rn
20260208143005OK0X-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L5128Rn
20260208145005OK0X-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L5128Rn
20260208151005OK0X-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L5128Rn
20260208153005OK0X-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L5128Rn
20260208155005OK0X-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L5128Rn
20260208161003OK0X-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5128Rn
20260208163003OK0X-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5128Rn
20260208165003OK0X-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5128Rn
20260208171003OK0X-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5128Rn
20260208173003OK0X-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5128Rn
20260208175003OK0X-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5128Rn
20260208181003OK0X-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5128Rn
20260208183004OK0X-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5128Rn
20260208185004OK0X-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5128Rn
20260208191004OK0X-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5128Rn
20260208191021OK0X-10>APLRG1,OK2ZAW-17*,qAS,OK1TPG-27:!L5128Rn