APRS Packet Errors for DL9EBF-5 (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
20260208170805DL9EBF-5>APRSMC,TCPIP*,qAR,DA6PLH-3:!5119.03N/00629.32E#/B=091/A=000148
20260208173810DL9EBF-5>APRSMC,TCPIP*,qAR,DA6PLH-3:!5119.03N/00629.32E#/B=091/A=000148
20260208183805DL9EBF-5>APRSMC,TCPIP*,qAR,DA6PLH-3:!5119.03N/00629.32E#/B=090/A=000148
20260208190809DL9EBF-5>APRSMC,TCPIP*,qAR,DA6PLH-3:!5119.03N/00629.32E#/B=090/A=000148
20260208193805DL9EBF-5>APRSMC,TCPIP*,qAR,DA6PLH-3:!5119.03N/00629.32E#/B=090/A=000148
20260208193855DL9EBF-5>APRSMC,TCPIP*,qAR,DL6EE-12:!5119.03N/00629.32E#/B=090/A=000148
20260208200805DL9EBF-5>APRSMC,TCPIP*,qAR,DA6PLH-3:!5119.03N/00629.32E#/B=090/A=000148
20260208203810DL9EBF-5>APRSMC,TCPIP*,qAR,DA6PLH-3:!5119.03N/00629.32E#/B=089/A=000148
20260208203905DL9EBF-5>APRSMC,TCPIP*,qAR,DL6EE-12:!5119.03N/00629.32E#/B=089/A=000148
20260208210812DL9EBF-5>APRSMC,TCPIP*,qAR,DA6PLH-3:!5119.03N/00629.32E#/B=089/A=000148
20260208210844DL9EBF-5>APRSMC,TCPIP*,qAR,DL6EE-12:!5119.03N/00629.32E#/B=089/A=000148
20260208213805DL9EBF-5>APRSMC,TCPIP*,qAR,DA6PLH-3:!5119.03N/00629.32E#/B=089/A=000148