APRS Packet Errors for N0XMZ (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
20260209114640N0XMZ>APX218,WIDE2-2,qAR,STJOMC:=3910.40N/09431.16Wx
20260209120610N0XMZ>APX218,WIDE2-2,qAO,N0ACT-10:=3910.40N/09431.16Wx
20260209124148N0XMZ>APX218,WIDE2-2,qAO,N0ACT-10:=3910.40N/09431.16Wx
20260209131149N0XMZ>APX218,WIDE2-2,qAR,STLUBR:=3910.40N/09431.16Wx
20260209134150N0XMZ>APX218,WIDE2-2,qAR,STLUBR:=3910.40N/09431.16Wx
20260209141602N0XMZ>APX218,WIDE2-2,qAO,N0ACT-10:=3910.40N/09431.16Wx
20260209144559N0XMZ>APX218,WIDE2-2,qAO,N0ACT-10:=3910.40N/09431.16Wx
20260209151604N0XMZ>APX218,WIDE2-2,qAR,STLSMI:=3910.40N/09431.16Wx
20260209154600N0XMZ>APX218,WIDE2-2,qAR,STLUBR:=3910.40N/09431.16Wx
20260209161601N0XMZ>APX218,WIDE2-2,qAR,KD0YUJ:=3910.40N/09431.16Wx
20260209164602N0XMZ>APX218,WIDE2-2,qAR,STLUBR:=3910.40N/09431.16Wx
20260209171603N0XMZ>APX218,WIDE2-2,qAR,STLUBR:=3910.40N/09431.16Wx