APRS Packet Errors for RA1AMW-0 (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
20260208164240RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208171229RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208174229RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208181228RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208184230RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208191228RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208194230RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208201230RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208204229RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208211229RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208214230RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny
20260208221230RA1AMW>APU25N,TCPIP*,qAC,T2ADG:;RA1AMW-0 *010917z6034.50N2940.54EUsunny