APRS Packet Errors for DK3ACH-11 (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
20260209104330DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=087/A=000712
20260209111345DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=100/A=000712
20260209114400DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=090/A=000712
20260209121415DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=078/A=000712
20260209124426DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=076/A=000712
20260209131442DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=087/A=000712
20260209134457DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=100/A=000712
20260209141513DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=074/A=000712
20260209144527DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=080/A=000712
20260209151538DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=069/A=000712
20260209154553DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=074/A=000712
20260209161608DK3ACH-11>APRSGW,TCPIP*,qAR,DK3ACH-11:!5024.75N/00809.55E_#DK3ACH-9/B=096/A=000712