APRS Packet Errors for OE6DVM-1 (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
20260209092943OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209100001OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209103016OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209110031OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209113046OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209120104OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209123119OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209130134OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209133149OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209140207OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209143222OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181
20260209150238OE6DVM-1>APRSGW,TCPIP*,qAR,OE6DVM-1:!4702.82N/01523.54E-#MeshCom/B=100/A=001181