APRS Packet Errors for EW3656 (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
20180720163606EW3656>APRS,TCPXX*,qAX,CWOP-7:@201636z51.3160 N/0.8894 E_234/000g001t073r000p005P005b10173h66L000.WD 166
20180720173106EW3656>APRS,TCPXX*,qAX,CWOP-3:@201731z51.3160 N/0.8894 E_225/001g003t071r000p005P005b10160h73L000.WD 166
20180720180106EW3656>APRS,TCPXX*,qAX,CWOP-7:@201801z51.3160 N/0.8894 E_337/000g003t070r000p005P005b10169h75L000.WD 166
20180720190106EW3656>APRS,TCPXX*,qAX,CWOP-3:@201901z51.3160 N/0.8894 E_180/000g002t068r000p005P005b10184h78L000.WD 166
20180720190605EW3656>APRS,TCPXX*,qAX,CWOP-7:@201906z51.3160 N/0.8894 E_031/000g001t068r000p005P005b10186h79L000.WD 166
20180720193106EW3656>APRS,TCPXX*,qAX,CWOP-4:@201931z51.3160 N/0.8894 E_225/000g002t067r000p005P005b10196h80L000.WD 166
20180720193606EW3656>APRS,TCPXX*,qAX,CWOP-4:@201936z51.3160 N/0.8894 E_302/000g001t067r000p005P005b10198h80L000.WD 166
20180720210606EW3656>APRS,TCPXX*,qAX,CWOP-5:@202106z51.3160 N/0.8894 E_270/000g000t064r001p006P006b10228h88L000.WD 166
20180720213606EW3656>APRS,TCPXX*,qAX,CWOP-7:@202136z51.3160 N/0.8894 E_180/000g000t063r001p006P006b10238h90L000.WD 166
20180720220606EW3656>APRS,TCPXX*,qAX,CWOP-5:@202206z51.3160 N/0.8894 E_270/000g000t063r000p006P006b10224h91L000.WD 166