APRS Packet Errors for DL2SDR-99 (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
20260209155334DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209162334DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209165334DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209172334DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209175334DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209182334DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209185334DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209192334DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209195335DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209202335DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209205335DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072
20260209212335DL2SDR-99>APRSGW,TCPIP*,qAR,DL2SDR-99:!5348.55N/00938.14E#/B=100/A=000072