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
20260417112957MB7URG>APRX28,qAR,M0MST-1:!5PHG3030 RATS
20260417123357MB7URG>APRX28,qAO,G0CHO-10:;Gtar
20260417142103MB7URG>APRX28,qAO,G0CHO-10:;Gnஒd@c!5217.28NM00050.33WA000/000/A=000000G3MRK MOULTON UK
20260417142522MB7URG>APRX28,qAO,G0CHO-10:;Mz5223.48N/00114.72W#PHG3030 144.950 Packet
20260417143926MB7URG>APRX28,qAO,G0CHO-10:;GDStar
20260417151932MB7URG>APRX28,qAO,G0CHO-10:;M50 Packet
20260417155224MB7URG>APRX28,qAO,G0CHO-10:;Gd`@fnஒb@ஒd@e`w9Ml#/"4r}PicoAPRS by DB1NTO
20260417164246MB7URG>APRX28,qAO,G0CHO-10:;G *111111z5223.47N/00114.72WrPHG2160 RB06 433.150 +1600 A67