APRS Packet Errors for N9NMR-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
20230604203616N9NMR-3>BEACON,qAR,W9RCG-2:!4256.08N8802.62W
20230604205616N9NMR-3>BEACON,qAO,KB9OIV-2:!4256.08N8802.62W
20230604211616N9NMR-3>BEACON,qAR,KB9OIV-1:!4256.08N8802.62W
20230604213616N9NMR-3>BEACON,qAO,KB9OIV-2:!4256.08N8802.62W
20230604215616N9NMR-3>BEACON,qAR,KB9OIV-1:!4256.08N8802.62W
20230604221616N9NMR-3>BEACON,qAO,KB9OIV-2:!4256.08N8802.62W
20230604223616N9NMR-3>BEACON,qAR,KB9OIV-1:!4256.08N8802.62W
20230604225616N9NMR-3>BEACON,qAR,KB9OIV-1:!4256.08N8802.62W
20230604231617N9NMR-3>BEACON,qAR,KB9OIV-1:!4256.08N8802.62W
20230604233617N9NMR-3>BEACON,qAR,W9RCG-2:!4256.08N8802.62W
20230604235617N9NMR-3>BEACON,qAR,KB9OIV-1:!4256.08N8802.62W
20230605001617N9NMR-3>BEACON,qAR,KB9OIV-1:!4256.08N8802.62W
20230605003617N9NMR-3>BEACON,qAO,KB9OIV-2:!4256.08N8802.62W
20230605005617N9NMR-3>BEACON,qAO,KB9OIV-2:!4256.08N8802.62W
20230605013617N9NMR-3>BEACON,qAR,W9RCG-2:!4256.08N8802.62W
20230605015617N9NMR-3>BEACON,qAR,KB9OIV-1:!4256.08N8802.62W
20230605021617N9NMR-3>BEACON,qAO,KB9OIV-2:!4256.08N8802.62W