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
20260209090510FW0800>APN000,TCPXX*,qAX,CWOP-3:@090905z4521.44N/09335.50W_146/004g010t029r000p000P000b10180h79L000eMB63
20260209093510FW0800>APN000,TCPXX*,qAX,CWOP-6:@090935z4521.44N/09335.50W_230/004g011t029r000p000P000b10173h78L000eMB63
20260209100510FW0800>APN000,TCPXX*,qAX,CWOP-4:@091005z4521.44N/09335.50W_191/003g010t030r000p000P000b10170h77L000eMB63
20260209103515FW0800>APN000,TCPXX*,qAX,CWOP-5:@091035z4521.44N/09335.50W_214/002g008t029r000p000P000b10167h77L000eMB63
20260209110515FW0800>APN000,TCPXX*,qAX,CWOP-4:@091105z4521.44N/09335.50W_199/002g007t029r000p000P000b10162h77L000eMB63
20260209113514FW0800>APN000,TCPXX*,qAX,CWOP-5:@091135z4521.44N/09335.50W_193/002g007t030r000p000P000b10163h77L000eMB63
20260209130520FW0800>APN000,TCPXX*,qAX,CWOP-7:@091305z4521.44N/09335.50W_175/001g006t029r000p000P000b10154h79L000eMB63
20260209133520FW0800>APN000,TCPXX*,qAX,CWOP-5:@091335z4521.44N/09335.50W_198/002g006t030r000p000P000b10153h79L005eMB63
20260209140520FW0800>APN000,TCPXX*,qAX,CWOP-4:@091405z4521.44N/09335.50W_207/003g009t030r000p000P000b10154h78L032eMB63
20260209143520FW0800>APN000,TCPXX*,qAX,CWOP-7:@091435z4521.44N/09335.50W_162/001g005t031r000p000P000b10150h78L058eMB63