APRS Packet Errors for DL4ALA-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
20260209130021DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209133036DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209140052DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209143110DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209150125DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209153140DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209160155DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209163210DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209170225DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209173240DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209180255DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433
20260209183310DL4ALA-99>APRSGW,TCPIP*,qAR,DL4ALA-99:!5127.53N/01110.08E&#Andreas/B=100/A=000433