APRS Packet Errors for DF1BO-42 (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
20260208131046DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=071/A=000377
20260208134057DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=100/A=000377
20260208141112DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=040/A=000377
20260208144129DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=100/A=000377
20260208151145DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=100/A=000377
20260208154154DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=067/A=000377
20260208161212DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=100/A=000377
20260208164227DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=100/A=000377
20260208171245DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=038/A=000377
20260208174252DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=100/A=000377
20260208181307DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=100/A=000377
20260208184322DF1BO-42>APRSMC,TCPIP*,qAR,DF1BO-12:!5025.56N/00734.87E#test#e213/B=100/A=000377