APRS Packet Errors for DG4RN-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
20260208195244DG4RN-12>APRSGW,TCPIP*,qAR,DG4RN-12:!5259.90N/00913.69E##DG4RN-12/B=014/A=000200
20260208205310DG4RN-12>APRSGW,TCPIP*,qAR,DG4RN-12:!5259.90N/00913.69E##DG4RN-12/B=069/A=000203
20260208212325DG4RN-12>APRSGW,TCPIP*,qAR,DG4RN-12:!5259.90N/00913.69E##DG4RN-12/B=005/A=000226
20260208215342DG4RN-12>APRSGW,TCPIP*,qAR,DG4RN-12:!5259.90N/00913.69E##DG4RN-12/B=100/A=000223
20260208222357DG4RN-12>APRSGW,TCPIP*,qAR,DG4RN-12:!5259.90N/00913.68E##DG4RN-12/B=070/A=000217
20260208232425DG4RN-12>APRSGW,TCPIP*,qAR,DG4RN-12:!5259.90N/00913.68E##DG4RN-12/B=100/A=000217
20260208235440DG4RN-12>APRSGW,TCPIP*,qAR,DG4RN-12:!5259.90N/00913.68E##DG4RN-12/A=000217
20260209002456DG4RN-12>APRSGW,TCPIP*,qAR,DG4RN-12:!5259.90N/00913.68E##DG4RN-12/B=008/A=000213
20260209005511DG4RN-12>APRSGW,TCPIP*,qAR,DG4RN-12:!5259.90N/00913.68E##DG4RN-12/B=008/A=000213