APRS Packet Errors for DG4ABR-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
20260208130507DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=080/A=000581
20260208133522DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=080/A=000581
20260208140537DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=080/A=000581
20260208143552DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=080/A=000581
20260208150607DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=081/A=000581
20260208153625DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=080/A=000581
20260208160640DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=080/A=000581
20260208163655DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=080/A=000581
20260208170710DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=080/A=000581
20260208173729DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=080/A=000581
20260208180744DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=079/A=000581
20260208183759DG4ABR-99>APRSGW,TCPIP*,qAR,DG4ABR-99:!5152.72N/01008.26E##DG4ABR-0/B=080/A=000581