APRS Packet Errors for CHAIX (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
20260209115230CHAIX>APOT30,WIDE1-1,WIDE2-1,qAR,GTOWN:!3850.09N/12034.62W# 11.1V N6YBH
20260209122239CHAIX>APOT30,WIDE1-1,WIDE2-1,qAR,GTOWN:!3850.09N/12034.62W# 12.6V N6YBH
20260209125245CHAIX>APOT30,WIDE1-1,WIDE2-1,qAO,FRNKLN:!3850.09N/12034.62W# 12.6V N6YBH
20260209132251CHAIX>APOT30,WIDE1-1,WIDE2-1,qAO,FRNKLN:!3850.09N/12034.62W# 12.6V N6YBH
20260209135256CHAIX>APOT30,WIDE1-1,WIDE2-1,qAR,GAPGTE:!3850.09N/12034.62W# 12.6V N6YBH
20260209142259CHAIX>APOT30,WIDE1-1,WIDE2-1,qAR,KO6KL-10:!3850.09N/12034.62W# 12.5V N6YBH
20260209145309CHAIX>APOT30,WIDE1-1,WIDE2-1,qAR,GTOWN:!3850.09N/12034.62W# 12.5V N6YBH
20260209152312CHAIX>APOT30,WIDE1-1,WIDE2-1,qAO,FRNKLN:!3850.09N/12034.62W# 12.6V N6YBH
20260209155317CHAIX>APOT30,WIDE1-1,WIDE2-1,qAR,GTOWN:!3850.09N/12034.62W# 12.6V N6YBH
20260209162321CHAIX>APOT30,WIDE1-1,WIDE2-1,qAR,GTOWN:!3850.09N/12034.62W# 12.8V N6YBH
20260209165324CHAIX>APOT30,WIDE1-1,WIDE2-1,qAO,FRNKLN:!3850.09N/12034.62W# 13.1V N6YBH
20260209172331CHAIX>APOT30,WIDE1-1,WIDE2-1,qAO,KM6LYW-2:!3850.09N/12034.62W# 13.3V N6YBH