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
20250508065033MB7URG>APRX28,qAR,2E0TOY:!5Žà®’ˆŠd@áð`w6:lp)j/`"4v}145.500MHz www.ssiservis.org 73! IVAN M/OM0AIH _%
20250508082230MB7URG>APRX28,qAR,M0VDT-10:;G67
20250508104234MB7URG>APRX28,qAR,M0VDT-10:!5`žš`‚’îš„nª¤Žà®’ˆŠb@à®’ˆŠd@cð`vV/l
20250508145631MB7URG>APRX28,qAR,M0MST-1:;GWrPHG2160 RB06 433.150 +1600 A67
20250508235231MB7URG>APRX28,qAR,M0VDT-10:!5ª¤Žà®’ˆŠb@à®’ˆŠd@eð`w9MlE#/"4l}PicoAPRS by DB1NTO
20250509015232MB7URG>APRX28,qAR,M0MST-1:;Md¤¤¤dŽ`®®@fš„nª¤Žà®’ˆŠb@à®’ˆŠd@eð`w9Ml?#/"4h}PicoAPRS by DB1NTO
20250509040646MB7URG>APRX28,qAR,MB7UC:;Gtar
20250509043919MB7URG>APRX28,qAR,M0VDT-10:;GN/00114.72WrPHG2160 RB06 433.150 +1600 A67