APRS Packet Errors for N1FGY-10 (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
20260208152828N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-7:!4235.50NT07314.83W&PHG2130New Ashford
20260208155827N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-1:!4235.50NT07314.83W&PHG2130New Ashford
20260208162828N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-1:!4235.50NT07314.83W&PHG2130New Ashford
20260208165826N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-1:!4235.50NT07314.83W&PHG2130New Ashford
20260208172827N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-1:!4235.50NT07314.83W&PHG2130New Ashford
20260208175826N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-1:!4235.50NT07314.83W&PHG2130New Ashford
20260208182826N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-1:!4235.50NT07314.83W&PHG2130New Ashford
20260208185826N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-1:!4235.50NT07314.83W&PHG2130New Ashford
20260208192826N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-1:!4235.50NT07314.83W&PHG2130New Ashford
20260208202827N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-1:!4235.50NT07314.83W&PHG2130New Ashford
20260208205826N1FGY-10>APDW15,K1FFK-1,WIDE2*,qAR,W1DMR-1:!4235.50NT07314.83W&PHG2130New Ashford