APRS Packet Errors for KC0MGG-3 (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
20250420142126	KC0MGG-3>BEACON,WIDE-1,WIDE-2,qAR,WA0SDO-10:!39.1963N92.3400W
20250420152125	KC0MGG-3>BEACON,WIDE-1,WIDE-2,qAR,WA0SDO-10:!39.1963N92.3400W
20250420155125	KC0MGG-3>BEACON,WIDE-1,WIDE-2,qAR,WA0SDO-10:!39.1963N92.3400W
20250420162126	KC0MGG-3>BEACON,WIDE-1,WIDE-2,qAR,WA0SDO-10:!39.1963N92.3400W
20250420165125	KC0MGG-3>BEACON,WIDE-1,WIDE-2,qAR,WA0SDO-10:!39.1963N92.3400W
20250420172125	KC0MGG-3>BEACON,WIDE-1,WIDE-2,qAR,WA0SDO-10:!39.1963N92.3400W
20250420175125	KC0MGG-3>BEACON,WIDE-1,WIDE-2,qAR,WA0SDO-10:!39.1963N92.3400W
20250420182125	KC0MGG-3>BEACON,WIDE-1,WIDE-2,qAR,WA0SDO-10:!39.1963N92.3400W
20250420192125	KC0MGG-3>BEACON,WIDE-1,WIDE-2,qAR,WA0SDO-10:!39.1963N92.3400W
20250420195125	KC0MGG-3>BEACON,WIDE-1,WIDE-2,qAR,WA0SDO-10:!39.1963N92.3400W