APRS Packet Errors for G0TQM-2 (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
20251208112215G0TQM-2>APLRT1,WIDE1-1,qAR,G7NIR-10:!/3OsFMa*A_ Q.../...g...t...h..b10048
20251208113219G0TQM-2>APLRT1,WIDE1-1,qAR,G7NIR-10:!/3OsOMa*<_ ?Q.../...g...t...h..b10064portable SB:0 Bat=3.99V (84%)
20251208114222G0TQM-2>APLRT1,WIDE1-1,qAR,G7NIR-10:!/3OsWMa*D_ SQ.../...g...t...h..b10057
20251208115225G0TQM-2>APLRT1,WIDE1-1,qAR,G7NIR-10:!/3OsIMa*K_ wQ.../...g...t...h..b10054
20251208120228G0TQM-2>APLRT1,WIDE1-1,qAR,G7NIR-10:!/3OsSMa*<_ zQ.../...g...t...h..b10061
20251208121231G0TQM-2>APLRT1,WIDE1-1,qAO,G0TQM-11:!/3OsSMa*F_ vQ.../...g...t...h..b10060
20251208122234G0TQM-2>APLRT1,WIDE1-1,qAO,G0TQM-11:!/3OsMMa*g_ KQ.../...g...t...h..b10056
20251208132013G0TQM-2>APLRT1,WIDE1-1,qAO,G0TQM-11:!/3Os=Ma*o_ jQ.../...g...t...h..b10055
20251208133016G0TQM-2>APLRT1,WIDE1-1,qAO,G0TQM-11:!/3Os?Ma*j_ KQ.../...g...t...h..b10058
20251208134019G0TQM-2>APLRT1,WIDE1-1,qAO,G0TQM-11:!/3OsLMa*e_ CQ.../...g...t...h..b10057
20251208135022G0TQM-2>APLRT1,WIDE1-1,qAO,G0TQM-11:!/3OsSMa*c_ eQ.../...g...t...h..b10054
20251208140025G0TQM-2>APLRT1,WIDE1-1,qAO,G0TQM-11:!/3Os=Ma*l_ KQ.../...g...t...h..b10060