#RFFE
Live, measured metrics for the hashtag #RFFE from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rffe
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-11-12 12:13 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-11-12 12:13 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-11-12 12:13 UTCEverything below is measured over the latest 2 public posts (spanning ~28217 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
New (to me) devkit acquired. It's by WiSpry for their WS1050 digitally tuned capacitor. But the big thing for me is not the neat DTC, but that it is a known good, known working combination that talks RFFE to the DTC. So I have something to
#RFFE is a tangled web of existing and new low-, mid-, and high-spectrum bands, unlicensed bands
#rffe across platforms
every network with a public tag surfaceFollow #rffe straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/rffe