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
20190922074317KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20190922081314KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20190922084312KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KJ4NES-4:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20190922091309KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20190922094306KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KJ4NES-4:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20190922101303KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20190922104301KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20190922111258KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KJ4NES-4:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20190922114256KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KJ4NES-4:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20190922121253KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20190922124250KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi