APRS Packet Errors for W6CDO (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
20260209111534W6CDO>APN000,TCPXX*,qAX,CWOP-7:@091048z3731.95N/12216.10W_226/000g003t052r000p000P000b10249h91L000eMB61
20260209114812W6CDO>APN000,TCPXX*,qAX,CWOP-3:@091148z3731.95N/12216.10W_299/000g003t051r000p000P000b10244h90L000eMB61
20260209124814W6CDO>APN000,TCPXX*,qAX,CWOP-6:@091248z3731.95N/12216.10W_299/000g000t049r000p000P000b10241h92L000eMB61
20260209141543W6CDO>APN000,TCPXX*,qAX,CWOP-4:@091348z3731.95N/12216.10W_292/000g003t049r000p000P000b10238h92L000eMB61
20260209144816W6CDO>APN000,TCPXX*,qAX,CWOP-5:@091448z3731.95N/12216.10W_243/000g001t049r000p000P000b10235h91L000eMB61
20260209154819W6CDO>APN000,TCPXX*,qAX,CWOP-7:@091548z3731.95N/12216.10W_283/000g003t051r000p000P000b10235h90L024eMB61