APRS Packet Errors for MB7URG (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
20261024074314MB7URG>APRX28,qAR,M0MST-1:;G11z5223.47N/00114.72WrPHG2160 RB06 433.150 +1600 A67
20261024074747MB7URG>APRX28,qAO,G6JVY-10:;G8 DStar
20261024094124MB7URG>APRX28,qAR,M0MST-1:;MB7NRG *111111y5223.48N70(114.72W#PHG3030 144.!50 Paeket
20261024162747MB7URG>APRX28,qAO,G0OFC-4:;G00114.72WrPHG2160 RB06 433.150 +1600 A67
20261024175315MB7URG>APRX28,qAO,G0OFC-4:!514.72W#PHG3030 RATS
20261024183639MB7URG>APRX28,qAO,G0OFC-4:;Gd`@fnஒb@ஒd@e`w9Ml5#/"4h}PicoAPRS by DB1NTO
20261024193503MB7URG>APRX28,qAO,G6JVY-10:;M030 144.950 Packet