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
20260316011344MB7URG>APRX28,qAR,M0VDT-10:;M14.72W#PHG3030 144.950 Packet
20260316034510MB7URG>APRX28,qAR,M0VDT-10:;G60 RB06 433.150 +1600 A67
20260316040319MB7URG>APRX28,qAR,M0VDT-10:;GB3®bnàš„nªœ àš„nª¤Žà®’ˆŠb@à®’ˆŠd@cð!5209.98NS00101.74W#NH-RAYNET Potcote
20260316081955MB7URG>APRX28,qAR,M0VDT-10:;G2WrPHG3130 DVU58 DStar
20260316090918MB7URG>APRX28,qAR,M0VDT-10:;G72WrPHG2160 RB06 433.150 +1600 A67
20260316103009MB7URG>APRX28,qAR,M0VDT-10:;M 144.950 Packet
20260316103853MB7URG>APRX28,qAR,M0VDT-10:;G7
20260316115917MB7URG>APRX28,qAR,M0VDT-10:;MW#PHG3030 144.950 Packet
20260316123441MB7URG>APRX28,qAO,G0CHO-10:;M1z5223.48N/00114.72W#PHG3030 144.950 Packet
20260316150320MB7URG>APRX28,qAR,M0VDT-10:;G60 RB06 433.150 +1600 A67
20260316185540MB7URG>APRX28,qAR,2E0TOY:;GrPHG2160 RB06 433.150 +1600 A67
20260316211020MB7URG>APRX28,qAR,M0VDT-10:;MPacket
20260316222024MB7URG>APRX28,qAO,G0CHO-10:;M
20260316223818MB7URG>APRX28,qAR,M0VDT-10:;M144.950 Packet