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
20240620230527KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240620233524KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240621000521KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240621003518KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240621010515KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240621013515KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240621020512KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240621023509KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240621030506KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240621033503KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240621040500KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20240621043528KJ4NES-3>APTT4,WIDE1-1,qAR,KJ4ARE-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi