APRS Packet Errors for DL2EDF-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
20260208130945	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208134006	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208141029	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208144052	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208151116	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208154141	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208161202	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208164224	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208171246	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208174308	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208181329	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308
20260208184351	DL2EDF-12>APRSGW,TCPIP*,qAR,DL2EDF-12:!5106.63N/00627.78E-Juechen/A=000308