APRS Packet Errors for KJ4NES-3 (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
20260226201131KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260226204128KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260226211125KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260226214122KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260226221120KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260226224117KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260226231114KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260226234111KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260227001108KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260227001213KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260227004208KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260227011205KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20260227014203KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi