APRS Packet Errors for N5ODX (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
20250701204937N5ODX>N5ODX,qAR,W5GNB-10:/012049z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000
20250701211937N5ODX>N5ODX,qAR,W5GNB-10:/012119z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000
20250701221938N5ODX>N5ODX,qAR,W5GNB-10:/012219z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000
20250701224938N5ODX>N5ODX,qAR,W5GNB-10:/012249z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000
20250701231938N5ODX>N5ODX,qAR,W5GNB-10:/012319z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000
20250701234938N5ODX>N5ODX,qAR,W5GNB-10:/012349z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000
20250702001938N5ODX>N5ODX,qAR,W5GNB-10:/020019z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000
20250702004938N5ODX>N5ODX,qAR,W5GNB-10:/020049z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000
20250702011938N5ODX>N5ODX,qAR,W5GNB-10:/020119z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000
20250702014938N5ODX>N5ODX,qAR,W5GNB-10:/020149z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000
20250702021938N5ODX>N5ODX,qAR,W5GNB-10:/020219z0000.00N/00000.00E- N5ODX WE MONITOR 146520, 223500, 446000