APRS Packet Errors for DL5BTE-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
20260208150703DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220
20260208153718DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220
20260208160737DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220
20260208170805DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220
20260208173820DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220
20260208180835DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220
20260208183850DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220
20260208190905DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220
20260208193920DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220
20260208200933DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220
20260208203948DL5BTE-12>APRSGW,TCPIP*,qAR,DL5BTE-12:!5220.14N/01432.00E#/B=100/A=000220