APRS Packet Errors for TG9AFX-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
20260208131111TG9AFX-3>APOT21,WIDE1-1,qAR,TG9ASO:/131110h1437.71N/09033.39W#EPE014
20260208134119TG9AFX-3>APOT21,WIDE1-1,qAR,TG9ASO:/134117h1437.71N/09033.39W#EPE013
20260208141127TG9AFX-3>APOT21,WIDE1-1,qAR,TG9ASO:/141126h1437.71N/09033.39W#EPE013
20260208144137TG9AFX-3>APOT21,WIDE1-1,qAR,TG9ASO:/144136h1437.70N/09033.39W#EPE015
20260208151144TG9AFX-3>APOT21,WIDE1-1,qAR,TG9ASO:/151143h1437.71N/09033.39W#EPE011
20260208154152TG9AFX-3>APOT21,WIDE1-1,qAR,TG9ASO:/154151h1437.71N/09033.39W#EPE016
20260208161201TG9AFX-3>APOT21,WIDE1-1,qAR,TG9ASO:/161200h1437.71N/09033.39W#EPE010
20260208164209TG9AFX-3>APOT21,WIDE1-1,qAR,TG9ASO:/164208h1437.71N/09033.39W#EPE018
20260208171217TG9AFX-3>APOT21,WIDE1-1,qAR,TG9ASO:/171216h1437.71N/09033.39W#EPE011
20260208174231TG9AFX-3>APOT21,WIDE1-1,qAR,TG9JMR-10:/174230h1437.71N/09033.39W#EPE009
20260208181246TG9AFX-3>APOT21,WIDE1-1,qAR,TG9ASO:/181245h1437.71N/09033.39W#EPE009
20260208184300TG9AFX-3>APOT21,WIDE1-1,qAR,TG9JMR-10:/184259h1437.71N/09033.39W#EPE008