APRS Packet Errors for DF8DL-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
20260208143724DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=100/A=000210
20260208150739DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=096/A=000210
20260208153754DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=100/A=000210
20260208160809DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=100/A=000210
20260208163826DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=100/A=000210
20260208170841DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=100/A=000210
20260208173856DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=087/A=000210
20260208180910DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=093/A=000210
20260208183922DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=084/A=000210
20260208190937DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=090/A=000210
20260208193952DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=083/A=000210
20260208201007DF8DL-11>APRSGW,TCPIP*,qAR,DF8DL-11:!5143.64N/00707.01E-MeshCom GW Haltern/B=084/A=000210