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
20201020193417CW3794>APRS,TCPXX*,qAX,CWOP-5:@201934z0000.00N/00000.00W_165/000g003t091L724r000P000p000h19b10139VL1252
20201020203437CW3794>APRS,TCPXX*,qAX,CWOP-5:@202034z0000.00N/00000.00W_259/001g005t092L663r000P000p000h20b10129VL1252
20201020210448CW3794>APRS,TCPXX*,qAX,CWOP-3:@202104z0000.00N/00000.00W_155/000g002t093L617r000P000p000h20b10125VL1252
20201020223441CW3794>APRS,TCPXX*,qAX,CWOP-4:@202234z0000.00N/00000.00W_154/000g002t094L383r000P000p000h19b10117VL1252
20201020230402CW3794>APRS,TCPXX*,qAX,CWOP-7:@202304z0000.00N/00000.00W_243/000g001t093L282r000P000p000h19b10115VL1252
20201020233414CW3794>APRS,TCPXX*,qAX,CWOP-4:@202334z0000.00N/00000.00W_241/000g001t093L182r000P000p000h18b10114VL1252
20201021003424CW3794>APRS,TCPXX*,qAX,CWOP-4:@210034z0000.00N/00000.00W_240/000g001t089L019r000P000p000h20b10113VL1252