APRS Packet Errors for dw6699 (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
20171125041013dw6699>APRS,TCPXX*,qAX,CWOP-7:@250410z3239.86N/09810.100W_164/000g000t062P000h44b09994ws31
20171125042014dw6699>APRS,TCPXX*,qAX,CWOP-7:@250420z3239.86N/09810.100W_155/003g000t062P000h44b09994ws31
20171125043014dw6699>APRS,TCPXX*,qAX,CWOP-7:@250430z3239.86N/09810.100W_150/000g000t062P000h45b09995ws31
20171125044013dw6699>APRS,TCPXX*,qAX,CWOP-7:@250440z3239.86N/09810.100W_161/000g000t062P000h45b09996ws31
20171125045013dw6699>APRS,TCPXX*,qAX,CWOP-7:@250450z3239.86N/09810.100W_165/003g000t062P000h45b09996ws31
20171125050013dw6699>APRS,TCPXX*,qAX,CWOP-7:@250500z3239.86N/09810.100W_157/005g000t062P000h45b09997ws31
20171125051014dw6699>APRS,TCPXX*,qAX,CWOP-5:@250510z3239.86N/09810.100W_154/005g000t062P000h45b09998ws31
20171125052014dw6699>APRS,TCPXX*,qAX,CWOP-3:@250520z3239.86N/09810.100W_171/003g000t062P000h45b09999ws31