APRS Packet Errors for DK8RG-14 (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
20260209120716DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209123731DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209130746DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209133801DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209140816DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209143831DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209150846DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209153901DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209160916DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209163933DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209170947DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381
20260209174002DK8RG-14>APRSMC,TCPIP*,qAR,DK8RG-13:!5039.49N/01221.36E[MeshCom mobil#DK8RG-14/A=001381