APRS Packet Errors for N0EXE-3 (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
20260404141029N0EXE-3>BEACON,qAR,KC9DGP:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404144030N0EXE-3>BEACON,qAR,KC9DGP:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404151029N0EXE-3>BEACON,qAR,KC9DGP:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404154029N0EXE-3>BEACON,qAR,KC9DGP:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404161029N0EXE-3>BEACON,qAR,W0NE-3:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404164029N0EXE-3>BEACON,qAR,KC9DGP:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404171029N0EXE-3>BEACON,qAR,KC9DGP:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404174029N0EXE-3>BEACON,qAR,KC9DGP:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404181029N0EXE-3>BEACON,qAR,KC9DGP:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404184029N0EXE-3>BEACON,qAR,KC9DGP:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404191029N0EXE-3>BEACON,qAR,W0NE-3:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994
20260404194029N0EXE-3>BEACON,qAR,KC9DGP-2:;444.750+*000000z4348.68N/09114.97Wm N0EXE Tsq131.8 IRLP 4994