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
20171212010815EW66880>APRS,TCPXX*,qAX,CWOP-4:@120108z0000.00N/00000.00E_222/000g000t037P000h85b10142ws31
20171212020808EW66880>APRS,TCPXX*,qAX,CWOP-7:@120208z0000.00N/00000.00E_235/000g001t038P000h83b10136ws31
20171212030813EW66880>APRS,TCPXX*,qAX,CWOP-7:@120308z0000.00N/00000.00E_235/000g000t036P000h87b10130ws31
20171212040804EW66880>APRS,TCPXX*,qAX,CWOP-3:@120408z0000.00N/00000.00E_239/001g005t044P000h74b10122ws31
20171212050810EW66880>APRS,TCPXX*,qAX,CWOP-5:@120508z0000.00N/00000.00E_259/000g003t044P000h73b10111ws31
20171212060817EW66880>APRS,TCPXX*,qAX,CWOP-6:@120608z0000.00N/00000.00E_256/003g009t045P000h72b10101ws31