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
20170819040547EW66880>APRS,TCPXX*,qAX,CWOP-5:@190405z0000.00N/00000.00E_326/000g000t074P000h97b10132ws31
20170819050530EW66880>APRS,TCPXX*,qAX,CWOP-5:@190505z0000.00N/00000.00E_326/000g000t074P000h97b10133ws31
20170819060546EW66880>APRS,TCPXX*,qAX,CWOP-4:@190605z0000.00N/00000.00E_326/000g000t074P000h97b10131ws31
20170819070531EW66880>APRS,TCPXX*,qAX,CWOP-1:@190705z0000.00N/00000.00E_326/000g001t073P000h98b10129ws31
20170819080538EW66880>APRS,TCPXX*,qAX,CWOP-5:@190805z0000.00N/00000.00E_326/000g000t072P000h98b10127ws31
20170819090538EW66880>APRS,TCPXX*,qAX,CWOP-3:@190905z0000.00N/00000.00E_326/000g000t071P000h98b10129ws31