APRS Packet Errors for CW3794 (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
20200216143413CW3794>APRS,TCPXX*,qAX,CWOP-3:@161434z0000.00N/00000.00W_011/000g000t044L017r000P000p000h67b10216VL1252
20200216150433CW3794>APRS,TCPXX*,qAX,CWOP-7:@161504z0000.00N/00000.00W_010/000g004t047L095r000P000p000h66b10215VL1252
20200216153433CW3794>APRS,TCPXX*,qAX,CWOP-7:@161534z0000.00N/00000.00W_006/000g001t050L220r000P000p000h61b10216VL1252
20200216160422CW3794>APRS,TCPXX*,qAX,CWOP-7:@161604z0000.00N/00000.00W_006/000g000t054L326r000P000p000h55b10216VL1252
20200216163431CW3794>APRS,TCPXX*,qAX,CWOP-5:@161634z0000.00N/00000.00W_006/000g000t058L419r000P000p000h50b10216VL1252
20200216170408CW3794>APRS,TCPXX*,qAX,CWOP-5:@161704z0000.00N/00000.00W_006/000g000t059L506r000P000p000h46b10215VL1252
20200216180444CW3794>APRS,TCPXX*,qAX,CWOP-4:@161804z0000.00N/00000.00W_278/000g001t064L644r000P000p000h38b10213VL1252
20200216190405CW3794>APRS,TCPXX*,qAX,CWOP-4:@161904z0000.00N/00000.00W_121/000g004t067L730r000P000p000h35b10201VL1252
20200216193446CW3794>APRS,TCPXX*,qAX,CWOP-4:@161934z0000.00N/00000.00W_140/001g004t069L752r000P000p000h32b10194VL1252