APRS Packet Errors for DG6TOM-12 (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
20260208150511DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.56N/01140.39E[MeshCom-12/B=100/A=001473
20260208153511DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.60N/01140.42E[MeshCom-12/B=100/A=001529
20260208160512DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.42E[MeshCom-12/B=100/A=001644
20260208163512DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.43E[MeshCom-12/B=100/A=001644
20260208170512DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.42E[MeshCom-12/B=100/A=001585
20260208173512DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001585
20260208180512DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.59N/01140.42E[MeshCom-12/B=100/A=001591
20260208183512DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.60N/01140.41E[MeshCom-12/B=100/A=001624
20260208190512DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001663
20260208193513DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001591
20260208200513DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.40E[MeshCom-12/B=100/A=001526
20260208203513DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.42E[MeshCom-12/B=100/A=001542