APRS Packet Errors for DG9NL-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
20260208132748DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208135809DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208142829DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208145849DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208152910DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208155930DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208162950DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208170011DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208173031DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208180052DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208183112DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191
20260208190132DG9NL-12>APRSGW,TCPIP*,qAR,DG9NL-12:!4929.53N/01114.50E-hi#DG9NL-12/B=100/A=001191