APRS Packet Errors for DH2WS-17 (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
20260208145730DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208152745DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208155800DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208162815DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208165830DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208172845DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208175902DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208182917DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208185932DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208192947DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208200002DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853
20260208203017DH2WS-17>APRSGW,TCPIP*,qAR,DH2WS-17:!5043.17N/00727.09E#/A=000853