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
20251212090634KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212093631KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212100628KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212103625KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212110625KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212113623KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212120620KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KS5KY-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212123617KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212123707KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212130703KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212133700KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212140657KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20251212143654KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi