APRS Packet Errors for DL1GWN-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
20260209150031DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=091/A=002723
20260209153054DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=100/A=002723
20260209160116DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=100/A=002723
20260209163139DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=100/A=002723
20260209170201DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=091/A=002723
20260209173224DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=100/A=002723
20260209180249DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=100/A=002723
20260209183313DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=100/A=002723
20260209190336DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=100/A=002723
20260209193400DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=100/A=002723
20260209200423DL1GWN-12>APRSGW,TCPIP*,qAR,DL1GWN-12:!4750.64N/00755.61E-#dl1gwn-12/B=100/A=002723