APRS Packet Errors for GW4783 (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
20240619045142GW4783>APRS,TCPXX*,qAX,CWOP-6:/190451z0000.00N/00000.00E_143/001g002t069P000b10249h88cwMServer
20240619045822GW4783>APRS,TCPXX*,qAX,CWOP-7:/190458z0000.00N/00000.00E_158/001g002t068P000b10249h88cwMServer
20240619050502GW4783>APRS,TCPXX*,qAX,CWOP-4:/190505z0000.00N/00000.00E_171/001g002t068P000b10249h90cwMServer
20240619051142GW4783>APRS,TCPXX*,qAX,CWOP-7:/190511z0000.00N/00000.00E_151/001g002t068P000b10249h90cwMServer
20240619053142GW4783>APRS,TCPXX*,qAX,CWOP-7:/190531z0000.00N/00000.00E_286/000g001t067P000b10249h93cwMServer
20240619053823GW4783>APRS,TCPXX*,qAX,CWOP-7:/190538z0000.00N/00000.00E_186/001g001t067P000b10249h93cwMServer
20240619054502GW4783>APRS,TCPXX*,qAX,CWOP-3:/190545z0000.00N/00000.00E_167/001g001t067P000b10249h94cwMServer
20240619055822GW4783>APRS,TCPXX*,qAX,CWOP-3:/190558z0000.00N/00000.00E_189/001g001t066P000b10249h95cwMServer
20240619061142GW4783>APRS,TCPXX*,qAX,CWOP-3:/190611z0000.00N/00000.00E_170/001g002t066P000b10249h96cwMServer
20240619062502GW4783>APRS,TCPXX*,qAX,CWOP-7:/190625z0000.00N/00000.00E_169/001g002t065P000b10249h97cwMServer