APRS Packet Errors for OE1MOJ-8 (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
20260209095252OE1MOJ-8>APRSMC,TCPIP*,qAR,OE1GNR-12:!4813.70N/01620.16E#/B=100/A=000591
20260209102301OE1MOJ-8>APRSMC,TCPIP*,qAR,OE1GNR-12:!4813.70N/01620.16E#/B=100/A=000591
20260209105321OE1MOJ-8>APRSMC,TCPIP*,qAR,OE1KFR-13:!4813.70N/01620.16E#/B=100/A=000591
20260209112337OE1MOJ-8>APRSMC,TCPIP*,qAR,OE3MAG-12:!4813.70N/01620.16E#/B=100/A=000591
20260209115352OE1MOJ-8>APRSMC,TCPIP*,qAR,OE3MAG-12:!4813.70N/01620.16E#/B=100/A=000591
20260209125412OE1MOJ-8>APRSMC,TCPIP*,qAR,OE3MAG-12:!4813.70N/01620.16E#/B=100/A=000591
20260209132430OE1MOJ-8>APRSMC,TCPIP*,qAR,OE1GNR-12:!4813.70N/01620.16E#/B=100/A=000591
20260209135442OE1MOJ-8>APRSMC,TCPIP*,qAR,OE3MAG-12:!4813.70N/01620.16E#/B=100/A=000591
20260209142457OE1MOJ-8>APRSMC,TCPIP*,qAR,OE3MAG-12:!4813.70N/01620.16E#/B=100/A=000591