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
20181214144006EW66880>APRS,TCPXX*,qAX,CWOP-7:@141440z0000.00N/00000.00E_342/000g003t046P003h95b10116ws31
20181214154006EW66880>APRS,TCPXX*,qAX,CWOP-7:@141540z0000.00N/00000.00E_318/001g006t047P003h92b10130ws31
20181214164006EW66880>APRS,TCPXX*,qAX,CWOP-1:@141640z0000.00N/00000.00E_275/003g009t048P003h88b10138ws31
20181214174007EW66880>APRS,TCPXX*,qAX,CWOP-3:@141740z0000.00N/00000.00E_307/002g013t048P003h84b10131ws31
20181214184007EW66880>APRS,TCPXX*,qAX,CWOP-5:@141840z0000.00N/00000.00E_358/000g012t048P003h84b10133ws31
20181214194007EW66880>APRS,TCPXX*,qAX,CWOP-2:@141940z0000.00N/00000.00E_062/005g012t048P003h82b10129ws31