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
20260209115446DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.43N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000121
20260209122505DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.43N/01251.29E>DH1RGS on Tour#Steffen/B=100/A=000089
20260209131011DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.08N/01252.33E>DH1RGS on Tour#Steffen/B=100/A=000085
20260209134026DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.09N/01252.33E>DH1RGS on Tour#Steffen/B=100/A=000128
20260209141041DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.09N/01252.33E>DH1RGS on Tour#Steffen/B=100/A=000085
20260209144057DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.09N/01252.33E>DH1RGS on Tour#Steffen/B=100/A=000151
20260209151112DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.08N/01252.33E>DH1RGS on Tour#Steffen/B=100/A=000105
20260209154128DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.09N/01252.33E>DH1RGS on Tour#Steffen/B=100/A=000112
20260209161143DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.09N/01252.33E>DH1RGS on Tour#Steffen/B=100/A=000089
20260209164159DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.09N/01252.33E>DH1RGS on Tour#Steffen/B=100/A=000102
20260209171213DH1RGS-13>APRSMC,TCPIP*,qAR,DH1RGS-12:!5236.09N/01252.33E>DH1RGS on Tour#Steffen/B=100/A=000102