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
20241224121800KJ4NES-3>APTT4,WIDE1-1,qAR,KO4PVI-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224124757KJ4NES-3>APTT4,WIDE1-1,qAR,KO4PVI-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224125016KJ4NES-3>APTT4,N1DTA-1,W4CAT-1,WIDE2*,qAR,KM4ACK-2:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224131755KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224134752KJ4NES-3>APTT4,WIDE1-1,qAR,KO4PVI-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224141752KJ4NES-3>APTT4,WIDE1-1,qAR,KO4PVI-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224141826KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224144823KJ4NES-3>APTT4,WIDE1-1,qAR,KO4PVI-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224151822KJ4NES-3>APTT4,WIDE1-1,qAR,KO4PVI-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224154821KJ4NES-3>APTT4,WIDE1-1,qAR,KO4PVI-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224161820KJ4NES-3>APTT4,WIDE1-1,qAR,KO4PVI-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224164817KJ4NES-3>APTT4,WIDE1-1,qAR,KO4PVI-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20241224174812KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N1DTA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi