APRS Packet Errors for EW0236 (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
20181021192933EW0236>APRS,TCPXX*,qAX,CWOP-2:@211929z0000.00N/00000.00E_264/001g004t052r000p001P001h81b10202eCumulusFO
20181021193833EW0236>APRS,TCPXX*,qAX,CWOP-6:@211938z0000.00N/00000.00E_298/000g003t051r000p001P001h81b10203eCumulusFO
20181021194733EW0236>APRS,TCPXX*,qAX,CWOP-4:@211947z0000.00N/00000.00E_335/000g002t051r000p001P001h81b10204eCumulusFO
20181021195633EW0236>APRS,TCPXX*,qAX,CWOP-1:@211956z0000.00N/00000.00E_308/002g004t050r000p001P001h82b10206eCumulusFO