APRS Packet Errors for DG5DBY-2 (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
20260208153601DG5DBY-2>APRSMC,TCPIP*,qAR,DG5DBY-1:!5122.49N/00722.58E#/B=021/A=000381
20260208160608DG5DBY-2>APRSMC,TCPIP*,qAR,DG5DBY-1:!5122.49N/00722.58E#/B=017/A=000381
20260208163623DG5DBY-2>APRSMC,TCPIP*,qAR,DG5DBY-1:!5122.49N/00722.58E#/B=012/A=000381
20260208170638DG5DBY-2>APRSMC,TCPIP*,qAR,DG5DBY-1:!5122.49N/00722.58E#/B=009/A=000381
20260208173655DG5DBY-2>APRSMC,TCPIP*,qAR,DG5DBY-1:!5122.49N/00722.58E#/B=007/A=000381
20260208180710DG5DBY-2>APRSMC,TCPIP*,qAR,DG5DBY-1:!5122.49N/00722.58E#/B=005/A=000381
20260208190739DG5DBY-2>APRSMC,TCPIP*,qAR,DG5DBY-1:!5122.49N/00722.58E#/B=002/A=000381
20260208200808DG5DBY-2>APRSMC,TCPIP*,qAR,DG5DBY-1:!5122.49N/00722.58E#/A=000381
20260208203823DG5DBY-2>APRSMC,TCPIP*,qAR,DG5DBY-1:!5122.49N/00722.58E#/A=000381