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
20260209133516DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001558
20260209140516DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001558
20260209143516DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001558
20260209150516DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001558
20260209153516DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001558
20260209160516DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001558
20260209163517DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001558
20260209170517DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001568
20260209173517DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001594
20260209180517DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.60N/01140.39E[MeshCom-12/B=100/A=001594
20260209183517DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.58N/01140.42E[MeshCom-12/B=100/A=001578
20260209190518DG6TOM-12>APRSGW,TCPIP*,qAR,DG6TOM-12:!4813.57N/01140.45E[MeshCom-12/B=100/A=001847