APRS Packet Errors for DB9CR-20 (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
20260209140409	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.65Ee/B=100/A=001309
20260209143401	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.65Ee/B=100/A=001309
20260209150432	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.65Ee/B=100/A=001309
20260209153424	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.65Ee/B=100/A=001309
20260209160455	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.65Ee/B=100/A=001309
20260209163527	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.65Ee/B=100/A=001309
20260209170518	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.65Ee/B=100/A=001309
20260209173549	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.65Ee/B=100/A=001309
20260209180540	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.65Ee/B=100/A=001309