APRS Packet Errors for EW4762 (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
20180420235921EW4762>APRS,TCPXX*,qAX,CWOP-4:@202359z0000.00N/00000.00E_338/004g008t039r000p000P000h10b10223eCumulusFO
20180421000821EW4762>APRS,TCPXX*,qAX,CWOP-3:@210008z0000.00N/00000.00E_343/001g008t039r000p000P000h10b10225eCumulusFO
20180421001721EW4762>APRS,TCPXX*,qAX,CWOP-2:@210017z0000.00N/00000.00E_357/003g005t039r000p000P000h10b10228eCumulusFO
20180421002621EW4762>APRS,TCPXX*,qAX,CWOP-5:@210026z0000.00N/00000.00E_328/002g006t039r000p000P000h10b10230eCumulusFO
20180421003521EW4762>APRS,TCPXX*,qAX,CWOP-2:@210035z0000.00N/00000.00E_020/002g016t038r000p000P000h10b10231eCumulusFO
20180421004421EW4762>APRS,TCPXX*,qAX,CWOP-6:@210044z0000.00N/00000.00E_346/002g007t038r000p000P000h10b10232eCumulusFO