APRS Packet Errors for DW9751 (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
20171125041139DW9751>APRS,TCPXX*,qAX,CWOP-3:@250411z0000.00N/00000.00E_273/006g007t063P000b10159L000ws31
20171125042144DW9751>APRS,TCPXX*,qAX,CWOP-3:@250421z0000.00N/00000.00E_278/000g004t063P000b10159L000ws31
20171125043143DW9751>APRS,TCPXX*,qAX,CWOP-6:@250431z0000.00N/00000.00E_313/000g007t063P000b10157L000ws31
20171125044133DW9751>APRS,TCPXX*,qAX,CWOP-4:@250441z0000.00N/00000.00E_321/003g012t062P000b10159L000ws31
20171125045133DW9751>APRS,TCPXX*,qAX,CWOP-4:@250451z0000.00N/00000.00E_310/001g008t062P000b10162L000ws31
20171125050142DW9751>APRS,TCPXX*,qAX,CWOP-5:@250501z0000.00N/00000.00E_014/000g005t062P000b10163L000ws31
20171125051138DW9751>APRS,TCPXX*,qAX,CWOP-7:@250511z0000.00N/00000.00E_014/000g000t062P000b10165L000ws31
20171125052137DW9751>APRS,TCPXX*,qAX,CWOP-5:@250521z0000.00N/00000.00E_232/000g000t062P000b10162L000ws31