APRS Packet Errors for SP9VOM (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
20260208135809SP9VOM>APRS,WIDE1-1,WIDE2-2,qAR,SQ9OJV-1:!4935.50N/02036.00E-185/000/A=000872Robert DMR TG 26095 AT578
20260208140824SP9VOM>APRS,WIDE1-1,WIDE2-2,qAR,SQ9OJV-1:!4935.51N/02035.99E-008/000/A=001020Robert DMR TG 26095 AT578
20260208161010SP9VOM>APRS,WIDE1-1,WIDE2-2,qAR,SR7NST:!4935.53N/02036.01E-246/000/A=001200Robert DMR TG 26095 AT578
20260208162013SP9VOM>APRS,WIDE1-1,WIDE2-2,qAR,SQ9OJV-1:!4935.51N/02036.01E-182/000/A=001089Robert DMR TG 26095 AT578
20260208163725SP9VOM>APRS,WIDE1-1,WIDE2-2,qAR,SQ9OJV-1:!4935.52N/02036.01E-173/000/A=001053Robert DMR TG 26095 AT578