APRS Packet Errors for EW66880 (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
20180419034230EW66880>APRS,TCPXX*,qAX,CWOP-4:@190342z0000.00N/00000.00E_254/006g019t074P000h39b10077ws31
20180419044230EW66880>APRS,TCPXX*,qAX,CWOP-3:@190442z0000.00N/00000.00E_244/003g009t072P000h44b10076ws31
20180419054230EW66880>APRS,TCPXX*,qAX,CWOP-2:@190542z0000.00N/00000.00E_262/005g013t071P000h45b10072ws31
20180419064230EW66880>APRS,TCPXX*,qAX,CWOP-7:@190642z0000.00N/00000.00E_245/001g013t071P000h48b10066ws31
20180419074230EW66880>APRS,TCPXX*,qAX,CWOP-5:@190742z0000.00N/00000.00E_251/005g014t070P000h52b10065ws31
20180419084230EW66880>APRS,TCPXX*,qAX,CWOP-3:@190842z0000.00N/00000.00E_252/003g013t069P000h56b10064ws31