APRS Packet Errors for DC7OT-13 (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
20260209133536DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=100/A=000190
20260209140536DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=100/A=000190
20260209143536DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=100/A=000190
20260209150537DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=100/A=000190
20260209153537DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=059/A=000190
20260209160537DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=008/A=000190
20260209163537DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=009/A=000190
20260209170537DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=008/A=000190
20260209173537DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=100/A=000190
20260209180537DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=100/A=000190
20260209183537DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=059/A=000190
20260209190537DC7OT-13>APRSGW,TCPIP*,qAR,DC7OT-13:!5140.26N/00721.88E#Meshcom GW Datteln/B=070/A=000190