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
20180618115509EW66880>APRS,TCPXX*,qAX,CWOP-5:@181155z0000.00N/00000.00E_242/001g003t078P000h86b10191ws31
20180618125509EW66880>APRS,TCPXX*,qAX,CWOP-3:@181255z0000.00N/00000.00E_256/002g005t083P000h77b10193ws31
20180618135508EW66880>APRS,TCPXX*,qAX,CWOP-1:@181355z0000.00N/00000.00E_334/005g005t087P000h68b10192ws31
20180618145509EW66880>APRS,TCPXX*,qAX,CWOP-5:@181455z0000.00N/00000.00E_220/007g008t089P000h60b10190ws31
20180618155509EW66880>APRS,TCPXX*,qAX,CWOP-1:@181555z0000.00N/00000.00E_230/005g007t091P000h55b10190ws31
20180618165509EW66880>APRS,TCPXX*,qAX,CWOP-4:@181655z0000.00N/00000.00E_238/002g009t092P000h53b10186ws31