APRS Packet Errors for EA5JTT-11 (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
20260416160319EA5JTT-11>APRNFW,WIDE2-1,qAO,EA5JTT-10:!0000.00N/00000.00EO/A=000000/F0S0V2593C0I26T25H65P10135J0R4 NFWv65
20260416160323EA5JTT-11>APRNFW,WIDE2-1,qAO,EA5JTT-10:!0000.00N/00000.00EO/A=000000/F1S4V2603C0I26T25H65P10141J0R4 NFWv65
20260416160340EA5JTT-11>APRNFW,WIDE2-1,qAO,EA5JTT-10:!0000.00N/00000.00EO/A=000000/F2S4V2610C0I26T25H64P10154J0R4 NFWv65
20260416160345EA5JTT-11>APRNFW,WIDE2-1,qAO,EA5JTT-10:!0000.00N/00000.00EO/A=000000/F3S4V2593C0I26T24H64P10172J0R4 NFWv65
20260416160350EA5JTT-11>APRNFW,WIDE2-1,qAO,EA5JTT-10:!0000.00N/00000.00EO/A=000000/F4S4V2603C0I26T25H64P10169J0R4 NFWv65
20260416160404EA5JTT-11>APRNFW,WIDE2-1,qAO,EA5JTT-10:!0000.00N/00000.00EO/A=000000/F5S4V2586C0I26T25H63P10181J0R4 NFWv65
20260416160434EA5JTT-11>APRNFW,WIDE2-1,qAO,EA5JTT-10:!0000.00N/00000.00EO/A=000000/F6S4V2584C0I26T25H64P10172J0R4 NFWv65