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
20251215065629MB7URG>APRX28,qAR,2E0TOY:;M
20251215083313MB7URG>APRX28,qAR,M0VDT-10:;Gª¤Žà®’ˆŠb@à®’ˆŠd@eð!5220.62N0134.83Wk000/000/A=000452info@nehr.org.uk
20251215094445MB7URG>APRX28,qAO,G0CHO-10:;G RB06 433.150 +1600 A67
20251215094918MB7URG>APRX28,qAO,G0CHO-10:;G2WrPHG3130 DVU58 DStar
20251215134435MB7URG>APRX28,qAO,G0CHO-10:;GE *111111z5223.45N/00114.72WrPHG3130 DVU58 DStar
20251215145630MB7URG>APRX28,qAR,M0VDT-10:;G *111111z5223.45N/00114.72WrPHG3130 DVU58 DStar
20251215173354MB7URG>APRX28,qAR,M0VDT-10:;G7
20251215174300MB7URG>APRX28,qAR,M0VDT-10:;Mš„nªœ àš„nª¤Žà®’ˆŠb@à®’ˆŠd@cð!5209.98NS00101.74W#NH-RAYNET Potcote
20251215191305MB7URG>APRX28,qAR,2E0TOY:;M50 Packet
20251215194050MB7URG>APRX28,qAR,2E0TOY:;G223.47N/00114.72WrPHG2160 RB06 433.150 +1600 A67
20251215200311MB7URG>APRX28,qAR,2E0TOY:;GN/00114.72WrPHG3130 DVU58 DStar
20251215202029MB7URG>APRX28,qAR,2E0TOY:;GU58 DStar
20251215213708MB7URG>APRX28,qAR,2E0TOY:;MHG3030 144.950 Packet
20251215235032MB7URG>APRX28,qAR,M0MST-1:;G150 +1600 A67
20251216004924MB7URG>APRX28,qAR,2E0TOY:;G30 DVU58 DStar
20251216021513MB7URG>APRX28,qAR,M0VDT-10:;G.150 +1600 A67