APRS Packet Errors for EW3956 (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
20170622230054EW3956>APRS,TCPXX*,qAX,CWOP-3:/150348z0000.00N/00000.00E_201/010g012t080P002b10165h86cwMServer
20170622230734EW3956>APRS,TCPXX*,qAX,CWOP-5:/150355z0000.00N/00000.00E_207/010g012t080P002b10165h86cwMServer
20170622232054EW3956>APRS,TCPXX*,qAX,CWOP-5:/150408z0000.00N/00000.00E_207/009g012t080P002b10165h85cwMServer
20170622232734EW3956>APRS,TCPXX*,qAX,CWOP-3:/150415z0000.00N/00000.00E_215/010g012t080P002b10165h83cwMServer
20170623040053EW3956>APRS,TCPXX*,qAX,CWOP-3:/150848z0000.00N/00000.00E_199/016g019t080P000b10168h87cwMServer
20170623042053EW3956>APRS,TCPXX*,qAX,CWOP-3:/150908z0000.00N/00000.00E_196/015g017t080P000b10165h90cwMServer
20170623044053EW3956>APRS,TCPXX*,qAX,CWOP-4:/150928z0000.00N/00000.00E_194/014g016t080P000b10165h89cwMServer