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
20191208010442CW3794>APRS,TCPXX*,qAX,CWOP-7:@080104z0000.00N/00000.00W_248/001g003t065L000r000P000p000h56b10200VL1252
20191208020439CW3794>APRS,TCPXX*,qAX,CWOP-3:@080204z0000.00N/00000.00W_273/000g000t062L000r000P000p000h66b10201VL1252
20191208040417CW3794>APRS,TCPXX*,qAX,CWOP-4:@080404z0000.00N/00000.00W_282/000g000t059L000r002P004p004h81b10207VL1252
20191208043433CW3794>APRS,TCPXX*,qAX,CWOP-5:@080434z0000.00N/00000.00W_281/000g000t057L000r010P012p012h84b10206VL1252
20191208050409CW3794>APRS,TCPXX*,qAX,CWOP-4:@080504z0000.00N/00000.00W_282/000g000t057L000r011P015p015h85b10208VL1252
20191208053422CW3794>APRS,TCPXX*,qAX,CWOP-5:@080534z0000.00N/00000.00W_282/000g000t057L000r004P016p016h86b10207VL1252