APRS Packet Errors for FW0800 (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
20260208170457FW0800>APN000,TCPXX*,qAX,CWOP-7:@081704z4521.44N/09335.50W_117/003g011t033r000p000P000b10237h53L434eMB63
20260208180457FW0800>APN000,TCPXX*,qAX,CWOP-6:@081804z4521.44N/09335.50W_133/002g010t035r000p000P000b10233h51L483eMB63
20260208190457FW0800>APN000,TCPXX*,qAX,CWOP-3:@081904z4521.44N/09335.50W_063/004g010t036r000p000P000b10226h50L473eMB63
20260208193500FW0800>APN000,TCPXX*,qAX,CWOP-3:@081934z4521.44N/09335.50W_211/003g011t037r000p000P000b10224h49L448eMB63
20260208200500FW0800>APN000,TCPXX*,qAX,CWOP-3:@082004z4521.44N/09335.50W_186/003g010t038r000p000P000b10226h49L413eMB63
20260208203459FW0800>APN000,TCPXX*,qAX,CWOP-6:@082034z4521.44N/09335.50W_202/002g010t037r000p000P000b10220h51L364eMB63
20260208210459FW0800>APN000,TCPXX*,qAX,CWOP-6:@082104z4521.44N/09335.50W_186/003g009t038r000p000P000b10220h51L302eMB63
20260208213500FW0800>APN000,TCPXX*,qAX,CWOP-3:@082134z4521.44N/09335.50W_157/003g011t037r000p000P000b10217h52L214eMB63
20260208220500FW0800>APN000,TCPXX*,qAX,CWOP-5:@082204z4521.44N/09335.50W_180/002g010t036r000p000P000b10222h55L172eMB63