APRS Packet Errors for N8JLK-2 (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
20260208145852N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAO,N8JLK-7:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208152853N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAO,N8JLK-7:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208155854N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAO,N8JLK-7:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208162855N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAO,N8JLK-7:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208165856N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAO,N8JLK-7:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208172857N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAO,N8JLK-7:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208175858N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAR,NEWBRY:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208182859N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAR,NEWBRY:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208185900N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAO,N8JLK-7:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208192901N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAR,NEWBRY:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208195902N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAR,K8GI-5:=4121.47N/08141.21WxXastir on 16GB RPi5
20260208202903N8JLK-2>APX223,WIDE1-1,WIDE2-1,qAO,N8JLK-7:=4121.47N/08141.21WxXastir on 16GB RPi5