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
20251014012457MB7URG>APRX28,qAR,2E0TOY:;M3030 144.950 Packet
20251014020540MB7URG>APRX28,qAR,2E0TOY:!5.46N/00114.72W#PHG3030 RATS
20251014040138MB7URG>APRX28,qAR,2E0TOY:;G00114.72WrPHG3130 DVU58 DStar
20251014043958MB7URG>APRX28,qAR,2E0TOY:;M44.950 Packet
20251014081324MB7URG>APRX28,qAR,M0VDT-10:;MPacket
20251014095910MB7URG>APRX28,qAR,M0VDT-10:;G.45N/00114.72WrPHG3130 DVU58 DStar
20251014111116MB7URG>APRX28,qAR,M0VDT-10:;G8 DStar
20251014112952MB7URG>APRX28,qAO,MB7UUW:;Gtar
20251014121836MB7URG>APRX28,qAR,2E0TOY:;GB06 433.150 +1600 A67
20251014124633MB7URG>APRX28,qAO,M0XDC:;Mt
20251014130003MB7URG>APRX28,qAR,M0VDT-10:;G DVU58 DStar
20251014131312MB7URG>APRX28,qAR,2E0TOY:;GPHG2160 RB06 433.150 +1600 A67
20251014140147MB7URG>APRX28,qAR,2E0TOY:!5N/00114.72W#PHG3030 RATS
20251014144240MB7URG>APRX28,qAR,2E0TOY:;G14.72WrPHG2160 RB06 433.150 +1600 A67
20251014145941MB7URG>APRX28,qAR,2E0TOY:;G6 433.150 +1600 A67
20251014154853MB7URG>APRX28,qAR,2E0TOY:!5ª¤Žà®’ˆŠb@à®’ˆŠd@eð`w9LlR#/"4c}PicoAPRS by DB1NTO
20251014210416MB7URG>APRX28,qAR,2E0TOY:;MPacket