APRS Packet Errors for CW5863 (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
20190615214402CW5863>APRS,TCPXX*,qAX,CWOP-1:@152144z0000.00N/00000.00E_203/005g006t075P073h00b10175l1781ws31
20190615215402CW5863>APRS,TCPXX*,qAX,CWOP-5:@152154z0000.00N/00000.00E_235/010g022t075P105h00b10181l1781ws31
20190615220404CW5863>APRS,TCPXX*,qAX,CWOP-5:@152204z0000.00N/00000.00E_192/005g021t073P125h00b10173l1781ws31
20190615221403CW5863>APRS,TCPXX*,qAX,CWOP-2:@152214z0000.00N/00000.00E_312/000g006t072P135h00b10173l1781ws31
20190615222402CW5863>APRS,TCPXX*,qAX,CWOP-2:@152224z0000.00N/00000.00E_134/000g002t073P159h00b10182l1781ws31
20190615223404CW5863>APRS,TCPXX*,qAX,CWOP-5:@152234z0000.00N/00000.00E_082/000g001t074P186h00b10180l1781ws31
20190615224402CW5863>APRS,TCPXX*,qAX,CWOP-5:@152244z0000.00N/00000.00E_250/000g000t074P188h00b10180l1781ws31
20190615225402CW5863>APRS,TCPXX*,qAX,CWOP-6:@152254z0000.00N/00000.00E_080/000g002t074P188h00b10180l1781ws31
20190615230402CW5863>APRS,TCPXX*,qAX,CWOP-5:@152304z0000.00N/00000.00E_056/000g006t073P188h00b10186l1781ws31
20190615231402CW5863>APRS,TCPXX*,qAX,CWOP-2:@152314z0000.00N/00000.00E_020/000g000t073P189h00b10186l1781ws31