APRS Packet Errors for GB3NB (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
20260208132851MB7UNB>APN382,WIDE1-1,qAR,M9MTX:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208135851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208142851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208145851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208152851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208155851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208162851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208165851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208172851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208175851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208182851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060
20260208185851MB7UNB>APN382,WIDE1-1,qAR,MB7UGY:;GB3NB *011200z5233.89N/00118.69Er145.625MHz t094 -060