APRS Packet Errors for OE1RIG-4 (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
20260208150222OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.23EbQTH#Georg/B=019/A=001020
20260208153240OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.23EbQTH#Georg/B=020/A=001004
20260208160304OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.23EbQTH#Georg/B=021/A=001004
20260208163312OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.23EbQTH#Georg/B=020/A=001007
20260208170325OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.24EbQTH#Georg/B=021/A=001007
20260208173344OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.23EbQTH#Georg/B=020/A=001020
20260208180358OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.23EbQTH#Georg/B=020/A=000991
20260208183414OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.23EbQTH#Georg/B=021/A=000997
20260208190429OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.23EbQTH#Georg/B=041/A=001004
20260208193447OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.23EbQTH#Georg/B=021/A=001004
20260208200502OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.23EbQTH#Georg/B=020/A=001014
20260208203517OE1RIG-4>APRSMC,TCPIP*,qAR,OE1RIG-12:!4812.81N/01614.24EbQTH#Georg/B=024/A=001017