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
20260208165616	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.02N/01135.64Ee/B=096/A=001342
20260208172608	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.02N/01135.63Ee/B=100/A=001319
20260208182712	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.04N/01135.66Ee/B=100/A=001243
20260208185706	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.65Ee/B=100/A=001312
20260208192737	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.02N/01135.64Ee/B=100/A=001319
20260208195404	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.02N/01135.64Ee/B=100/A=001365
20260208202515	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.03N/01135.63Ee/B=100/A=001345
20260208205507	DB9CR-20>APRSMC,TCPIP*,qAR,DM0CR-20:!4955.02N/01135.64Ee/B=100/A=001355