APRS Packet Errors for DL3CR-9 (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
20260208133835	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=100/A=000981
20260208140900	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=100/A=000981
20260208143924	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=100/A=000981
20260208150947	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=100/A=000981
20260208153955	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=098/A=000981
20260208161000	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=100/A=000981
20260208164004	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=100/A=000981
20260208171008	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=098/A=000981
20260208174009	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=100/A=000981
20260208181036	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=096/A=000981
20260208184042	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=100/A=000981
20260208191045	DL3CR-9>APRSGW,TCPIP*,qAR,DL3CR-9:!4908.60N/00716.47E-/B=100/A=000981