APRS Packet Errors for MB7URG (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
20260426192819MB7URG>APRX28,qAR,M0MST-1:;G3.150 +1600 A67
20260426201312MB7URG>APRX28,qAO,G0CHO-10:;M Packet
20260426211219MB7URG>APRX28,qAO,G0CHO-10:!546N/00114.72W#PHG3030 RATS
20260426214847MB7URG>APRX28,qAO,G0CHO-10:!5#PHG3030 RATS
20260426215309MB7URG>APRX28,qAR,MB7VC:;G7
20260426225022MB7URG>APRX28,qAR,MB7VC:;G111111z5223.45N/00114.72WrPHG3130 DVU58 DStar
20260427003438MB7URG>APRX28,qAO,G0CHO-10:;G3.47N/00114.72WrPHG2160 RB06 433.150 +1600 A67