APRS Packet Errors for EW6654 (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
20190223064200EW6654>APRS,TCPXX*,qAX,CWOP-5:@230641z0000.00N/00000.00E_192/000g000t033P018h94b10188l1775ws31
20190223072332EW6654>APRS,TCPXX*,qAX,CWOP-4:@230723z0000.00N/00000.00E_192/000g000t033P018h94b10192l1775ws31
20190223085901EW6654>APRS,TCPXX*,qAX,CWOP-2:@230859z0000.00N/00000.00E_192/000g000t033P001h94b10195l1775ws31
20190223090900EW6654>APRS,TCPXX*,qAX,CWOP-6:@230909z0000.00N/00000.00E_192/000g000t033P001h94b10196l1775ws31
20190223091900EW6654>APRS,TCPXX*,qAX,CWOP-6:@230919z0000.00N/00000.00E_192/000g000t033P001h94b10198l1775ws31
20190223113857EW6654>APRS,TCPXX*,qAX,CWOP-2:@231138z0000.00N/00000.00E_192/000g000t033P001h94b10200l1775ws31
20190223114857EW6654>APRS,TCPXX*,qAX,CWOP-2:@231148z0000.00N/00000.00E_192/000g000t033P001h94b10201l1775ws31
20190223115857EW6654>APRS,TCPXX*,qAX,CWOP-1:@231158z0000.00N/00000.00E_192/000g000t033P001h94b10200l1775ws31