APRS Packet Errors for MB7URG (last 6 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
20260206162654MB7URG>APRX28,qAR,2E0TOY:;G‚ ˆ®bnàš„nªœ àš„nª¤Žà®’ˆŠb@à®’ˆŠd@cð!5209.98NS00101.74W#NH-RAYNET Potcote
20260206164830MB7URG>APRX28,qAO,G0CHO-10:;Gar
20260206180418MB7URG>APRX28,qAR,2E0TOY:;M3030 144.950 Packet
20260206195802MB7URG>APRX28,TCPIP*,qAC,T2CSNGRAD:!5223.46N/00114.72W#PHG3030 RATS
20260206201519MB7URG>APRX28,TCPIP*,qAC,T2CSNGRAD:!5223.46N/00114.72W#PHG3030 RATS
20260206203237MB7URG>APRX28,TCPIP*,qAC,T2CSNGRAD:!5223.46N/00114.72W#PHG3030 RATS
20260206205117MB7URG>APRX28,TCPIP*,qAC,T2CSNGRAD:!5223.46N/00114.72W#PHG3030 RATS
20260206210811MB7URG>APRX28,TCPIP*,qAC,T2CSNGRAD:!5223.46N/00114.72W#PHG3030 RATS
20260206212527MB7URG>APRX28,TCPIP*,qAC,T2CSNGRAD:!5223.46N/00114.72W#PHG3030 RATS
20260206214312MB7URG>APRX28,TCPIP*,qAC,T2CSNGRAD:!5223.46N/00114.72W#PHG3030 RATS
20260206220115MB7URG>APRX28,TCPIP*,qAC,T2CSNGRAD:!5223.46N/00114.72W#PHG3030 RATS