APRS Packet Errors for OE9AFV-3 (last 24 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
20250508091616OE9AFV-3>APRS,qAR,OE9XFV-10:!0000.00S/00000.00W3Alex, Tetra MTM5400
20250508091700OE9AFV-3>APRS,qAR,OE9XFV-10:!0000.00S/00000.00W3Alex, Tetra MTM5400
20250508091800OE9AFV-3>APRS,qAR,OE9XFV-10:!0000.00S/00000.00W3Alex, Tetra MTM5400
20250508091900OE9AFV-3>APRS,qAR,OE9XFV-10:!0000.00S/00000.00W3Alex, Tetra MTM5400
20250508092000OE9AFV-3>APRS,qAR,OE9XFV-10:!0000.00S/00000.00W3Alex, Tetra MTM5400
20250508092100OE9AFV-3>APRS,qAR,OE9XFV-10:!0000.00S/00000.00W3Alex, Tetra MTM5400
20250508092200OE9AFV-3>APRS,qAR,OE9XFV-10:!0000.00S/00000.00W3Alex, Tetra MTM5400