APRS Packet Errors for DH6WS-10 (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
20260208132826DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208135841DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208142852DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208145907DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208152922DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208155940DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208162955DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208170007DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208173022DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208180036DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208183051DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256
20260208190106DH6WS-10>APRSGW,TCPIP*,qAR,DH6WS-10:!5150.57N0816.59E#meshcom#DH6WS-10/B=100/A=000256