APRS Packet Errors for DL7AOD-12 (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
20260209133616DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=076
20260209140625DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=075
20260209143639DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=076
20260209150647DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=075
20260209153701DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=076
20260209160710DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=076
20260209163724DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=076
20260209170733DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=075
20260209173746DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=075
20260209180755DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=076
20260209183808DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=075
20260209190816DL7AOD-12>APRSGW,TCPIP*,qAR,DL7AOD-12:!5233.02N/01320.28E-Plötzensee#DL7AOD-10/B=076