APRS Packet Errors for DG1FBP-10 (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
20260208164741DG1FBP-10>APRSMC,TCPIP*,qAR,DG1FBP-12:!5039.85N/00810.64E>/B=100/A=001726
20260208171756DG1FBP-10>APRSMC,TCPIP*,qAR,DG1FBP-12:!5039.85N/00810.64E>/B=100/A=001726
20260208174811DG1FBP-10>APRSMC,TCPIP*,qAR,DG1FBP-12:!5039.85N/00810.64E>/B=100/A=001726
20260208181822DG1FBP-10>APRSMC,TCPIP*,qAR,DG1FBP-12:!5039.85N/00810.64E>/B=100/A=001726
20260208184837DG1FBP-10>APRSMC,TCPIP*,qAR,DG1FBP-12:!5039.85N/00810.64E>/B=100/A=001726
20260208191852DG1FBP-10>APRSMC,TCPIP*,qAR,DG1FBP-12:!5039.85N/00810.64E>/B=100/A=001726
20260208194911DG1FBP-10>APRSMC,TCPIP*,qAR,DG1FBP-12:!5039.85N/00810.64E>/B=100/A=001726
20260208201926DG1FBP-10>APRSMC,TCPIP*,qAR,DG1FBP-12:!5039.85N/00810.64E>/B=100/A=001726
20260208204941DG1FBP-10>APRSMC,TCPIP*,qAR,DG1FBP-12:!5039.85N/00810.64E>/B=100/A=001726
20260208211952DG1FBP-10>APRSMC,TCPIP*,qAR,DG1FBP-12:!5039.85N/00810.64E>/B=086/A=001726