APRS Packet Errors for EW6566 (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
20200710065709EW6566>APRS,TCPXX*,qAX,CWOP-7:@100657z522113.00N/0051802.00E_309/000g000t057r000p000P000b10084h00L012eMH51
20200710070211EW6566>APRS,TCPXX*,qAX,CWOP-3:@100702z522113.00N/0051802.00E_309/000g000t057r000p000P000b10084h00L011eMH51
20200710070708EW6566>APRS,TCPXX*,qAX,CWOP-7:@100707z522113.00N/0051802.00E_309/000g000t057r000p000P000b10086h00L019eMH51
20200710071209EW6566>APRS,TCPXX*,qAX,CWOP-4:@100712z522113.00N/0051802.00E_308/000g000t057r000p000P000b10086h00L009eMH51
20200710072709EW6566>APRS,TCPXX*,qAX,CWOP-7:@100727z522113.00N/0051802.00E_292/000g000t057r000p000P000b10090h00L007eMH51
20200710073710EW6566>APRS,TCPXX*,qAX,CWOP-7:@100737z522113.00N/0051802.00E_288/000g000t057r000p000P000b10091h00L009eMH51
20200710075218EW6566>APRS,TCPXX*,qAX,CWOP-5:@100752z522113.00N/0051802.00E_279/000g000t057r000p000P000b10094h00L005eMH51
20200710075708EW6566>APRS,TCPXX*,qAX,CWOP-7:@100757z522113.00N/0051802.00E_279/000g000t057r000p000P000b10096h00L007eMH51
20200710080209EW6566>APRS,TCPXX*,qAX,CWOP-4:@100802z522113.00N/0051802.00E_279/000g000t057r000p000P000b10097h00L009eMH51
20200710081708EW6566>APRS,TCPXX*,qAX,CWOP-3:@100817z522113.00N/0051802.00E_281/000g000t057r000p000P000b10100h00L011eMH51