APRS Packet Errors for DB0CRE-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
20260209103317DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260209110330DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260209113345DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/A=000397
20260209120401DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=004/A=000397
20260209123416DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/A=000397
20260209130431DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=002/A=000397
20260209133446DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260209140501DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260209143517DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/A=000397
20260209150532DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260209153547DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260209160602DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397