APRS Packet Errors for EW6205 (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
20171021222238EW6205>APRS,TCPXX*,qAX,CWOP-7:@212222z4809.-2N/10337.37W_327/009g...t051r...p...P...b10035h56eMH50
20171021222709EW6205>APRS,TCPXX*,qAX,CWOP-3:@212227z4809.-2N/10337.37W_316/008g...t051r...p...P...b10036h56eMH50
20171021223709EW6205>APRS,TCPXX*,qAX,CWOP-4:@212237z4809.-2N/10337.37W_308/009g019t051r000p000P000b10036h55eMH50
20171021225209EW6205>APRS,TCPXX*,qAX,CWOP-4:@212252z4809.-2N/10337.37W_312/009g019t052r000p000P000b10038h53eMH50
20171021225708EW6205>APRS,TCPXX*,qAX,CWOP-5:@212257z4809.-2N/10337.37W_303/010g021t052r000p000P000b10039h53eMH50