APRS Packet Errors for DG6TOM-11 (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
20260209133651DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=067/A=001752
20260209140653DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=068/A=001752
20260209143654DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=068/A=001752
20260209150656DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=068/A=001752
20260209153654DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=067/A=001752
20260209163658DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=067/A=001752
20260209170656DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=068/A=001752
20260209173652DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=069/A=001752
20260209180659DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=067/A=001752
20260209183659DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=068/A=001752
20260209190704DG6TOM-11>APRSMC,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.44E-DG6TOM-11 MeshCom/B=068/A=001752