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
20170501002840EW66880>APRS,TCPXX*,qAX,CWOP-4:@010028z0000.00N/00000.00E_327/000g000t073P001h90b10172ws31
20170501012841EW66880>APRS,TCPXX*,qAX,CWOP-5:@010128z0000.00N/00000.00E_222/000g005t073P001h86b10174ws31
20170501022840EW66880>APRS,TCPXX*,qAX,CWOP-6:@010228z0000.00N/00000.00E_290/000g005t072P001h85b10177ws31
20170501032841EW66880>APRS,TCPXX*,qAX,CWOP-3:@010328z0000.00N/00000.00E_147/000g006t071P001h87b10174ws31
20170501042841EW66880>APRS,TCPXX*,qAX,CWOP-2:@010428z0000.00N/00000.00E_279/001g009t071P000h90b10170ws31
20170501052841EW66880>APRS,TCPXX*,qAX,CWOP-2:@010528z0000.00N/00000.00E_042/001g008t070P000h91b10171ws31