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
20260429154826MB7URG>APRX28,qAR,M0MST-1:;M Packet
20260429161511MB7URG>APRX28,qAO,G0CHO-10:;G *111111z5223.47N/00114.72WrPHG2160 RB06 433.150 +1600 A67
20260429164133MB7URG>APRX28,qAO,G0CHO-10:;M50 Packet
20260429180100MB7URG>APRX28,qAO,G0CHO-10:;G +1600 A67
20260429180523MB7URG>APRX28,qAO,G0CHO-10:;GU58 DStar
20260429201728MB7URG>APRX28,qAS,MB7UMK-10:;M*111111z5223.48N/00114.72W#PHG3030 144.950 Packet
20260429212006MB7URG>APRX28,qAO,G0CHO-10:;G67
20260429220017MB7URG>APRX28,qAO,G0CHO-10:;G DStar
20260429220847MB7URG>APRX28,qAS,MB7UMK-10:!5PHG3030 RATS
20260429235147MB7URG>APRX28,qAS,MB7UMK-10:;M *111111z5223.48N/00114.72W#PHG3030 144.950 Packet
20260430023206MB7URG>APRX28,qAS,MB7UMK-10:;G00114.72WrPHG3130 DVU58 DStar
20260430030314MB7URG>APRX28,qAO,G0CHO-10:;G.72WrPHG2160 RB06 433.150 +1600 A67
20260430064359MB7URG>APRX28,qAO,G0CHO-10:;G1111z5223.45N/00114.72WrPHG3130 DVU58 DStar
20260430070727MB7URG>APRX28,qAO,G0CHO-10:;M Packet
20260430082813MB7URG>APRX28,qAO,G6JVY-10:;G4.72WrPHG2160 RB06 433.150 +1600 A67
20260430102916MB7URG>APRX28,qAS,MB7UMK-10:!5HG3030 RATS