APRS Packet Errors for DB3EH-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
20260209093412DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/B=100/A=000436
20260209093855DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/B=100/A=000436
20260209100910DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/A=000436
20260209103925DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/B=002/A=000436
20260209110940DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/B=100/A=000436
20260209113956DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/B=100/A=000436
20260209121011DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/A=000436
20260209124026DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/B=100/A=000436
20260209131044DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/B=100/A=000436
20260209134059DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/B=100/A=000436
20260209141114DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/A=000436
20260209144129DB3EH-12>APRSGW,TCPIP*,qAR,DB3EH-12:!5214.79N/00903.43E-/B=100/A=000436