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
20170816200954EW3956>APRS,TCPXX*,qAX,CWOP-5:/162009z0000.00N/00000.00E_146/010g010t083P000b10134h77cwMServer
20170816201624EW3956>APRS,TCPXX*,qAX,CWOP-5:/162016z0000.00N/00000.00E_150/009g012t083P000b10131h75cwMServer
20170816202304EW3956>APRS,TCPXX*,qAX,CWOP-3:/162023z0000.00N/00000.00E_151/010g012t084P000b10131h75cwMServer
20170816204944EW3956>APRS,TCPXX*,qAX,CWOP-5:/162049z0000.00N/00000.00E_131/007g010t084P000b10131h73cwMServer
20170816210944EW3956>APRS,TCPXX*,qAX,CWOP-4:/162109z0000.00N/00000.00E_095/008g010t084P000b10134h75cwMServer
20170816212304EW3956>APRS,TCPXX*,qAX,CWOP-4:/162123z0000.00N/00000.00E_054/012g016t084P000b10134h74cwMServer
20170816213624EW3956>APRS,TCPXX*,qAX,CWOP-3:/162136z0000.00N/00000.00E_319/009g016t083P000b10138h73cwMServer
20170816214304EW3956>APRS,TCPXX*,qAX,CWOP-4:/162143z0000.00N/00000.00E_323/010g016t080P007b10141h77cwMServer