#220mhz
Live, measured metrics for the hashtag #220mhz from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #220mhz
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mas.to (Mastodon public tags API) · fetched 2026-07-29 23:41 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-29 23:41 UTCNo related tags with measured usage found for #220mhz.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-29 23:41 UTCEverything below is measured over the latest 4 public posts (spanning ~21565 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0.3
Used together with
Top of the latest posts
A few months back I purchased an older Alinco DR-235 #220mhz transceiver at a local hamfest. I’d had my eye on it for a few hours (my club, I was doing photos, so there all day) and at the end of the day it had gotten no love. Price was dow
More #220mhz fun for the holidays, as Matt #W8MAP tried to contact me while I was testing the ARROW repeater on 220 and didn't get through to me. Something to debug.
My #Quansheng UV-K5 has at least vestigial capabilities on the #220mhz band, using Egzumer firmware. I put the 1.25m frequency for the ARROW repeater into the radio with CHIRP, and I'm able to use the spectrum monitor to see that it's heari
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/220mhz