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
20171119163247EW66880>APRS,TCPXX*,qAX,CWOP-4:@191632z0000.00N/00000.00E_311/006g009t058P001h42b10111ws31
20171119173317EW66880>APRS,TCPXX*,qAX,CWOP-6:@191733z0000.00N/00000.00E_287/006g011t058P001h38b10108ws31
20171119183311EW66880>APRS,TCPXX*,qAX,CWOP-2:@191833z0000.00N/00000.00E_344/002g010t059P001h34b10108ws31
20171119193306EW66880>APRS,TCPXX*,qAX,CWOP-6:@191933z0000.00N/00000.00E_309/004g011t059P001h34b10108ws31
20171119203248EW66880>APRS,TCPXX*,qAX,CWOP-6:@192032z0000.00N/00000.00E_334/003g007t058P001h36b10113ws31
20171119213249EW66880>APRS,TCPXX*,qAX,CWOP-3:@192132z0000.00N/00000.00E_321/003g009t056P001h39b10122ws31