APRS Packet Errors for DH1RGS-13 (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
20260208131017DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.43N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000118
20260208134037DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.43N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000105
20260208141057DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.44N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000085
20260208144117DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.43N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000082
20260208151137DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.44N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000115
20260208161217DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.43N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000085
20260208164237DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.43N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000082
20260208171258DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.43N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000079
20260208174316DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.44N/01251.30E>DH1RGS on Tour#Steffen/B=100/A=000066
20260208181336DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.43N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000066
20260208184356DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.43N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000102