APRS Packet Errors for DG1GHR-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
20260208170030DG1GHR-12>APRSMC,TCPIP*,qAR,DL2GAK-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459
20260208173026DG1GHR-12>APRSMC,TCPIP*,qAR,DL2GAK-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459
20260208180031DG1GHR-12>APRSMC,TCPIP*,qAR,DL2GAK-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459
20260208190034DG1GHR-12>APRSMC,TCPIP*,qAR,DL2GAK-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459
20260208190107DG1GHR-12>APRSMC,TCPIP*,qAR,DL6UF-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459
20260208200039DG1GHR-12>APRSMC,TCPIP*,qAR,DL2GAK-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459
20260208200115DG1GHR-12>APRSMC,TCPIP*,qAR,DL6UF-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459
20260208203023DG1GHR-12>APRSMC,TCPIP*,qAR,DL2GAK-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459
20260208203117DG1GHR-12>APRSMC,TCPIP*,qAR,DL6UF-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459
20260208210025DG1GHR-12>APRSMC,TCPIP*,qAR,DL2GAK-12:!4836.59N/00801.76E#MeshCom-GW/B=095/A=000459
20260208213024DG1GHR-12>APRSMC,TCPIP*,qAR,DL2GAK-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459
20260208220025DG1GHR-12>APRSMC,TCPIP*,qAR,DL6UF-12:!4836.59N/00801.76E#MeshCom-GW/B=100/A=000459