APRS Packet Errors for DO3DDF-1 (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
20260208130753DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=051/A=000259
20260208133812DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=036/A=000259
20260208140827DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=040/A=000259
20260208143838DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=017/A=000259
20260208150853DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=056/A=000259
20260208153908DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=022/A=000259
20260208160923DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=051/A=000259
20260208163938DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=028/A=000259
20260208170949DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=051/A=000259
20260208174004DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=054/A=000259
20260208181019DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=048/A=000259
20260208184034DO3DDF-1>APRSGW,TCPIP*,qAR,DO3DDF-1:!5138.39N/00715.47E#/B=046/A=000259