#rimfire
Live, measured metrics for the hashtag #rimfire from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rimfire
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-08-11 20:38 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-08-11 20:38 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-11 20:38 UTCEverything below is measured over the latest 6 public posts (spanning ~106009 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 1.2
Top of the latest posts
#NIFC #wildfires #firewx NIFC New Or Updated Wildfire Perimeter Incident Name: Rim Acres: 10.0 acres Updated: Nov 12, 2025 20:44 UTC Source: IRWIN #RimFire #TXwx
.@stevensjt is taking us on a Google Earth photo tour of the #RimFire. Mind blowing.
#CAwx Morning fire numbers. NOTE: Info is several hours old. #ShellyFire ACRES: 15,460 CONTAINMENT: 18% #HillFire ACRES: 4,989. CONTAINMENT: 0% #LakeFire ACRES: 38,664 CONTAINMENT: 73% #TroutFire ACRES: 11,489 CONTAINMENT: 0% #LongFire ACRE
#rimfire across platforms
every network with a public tag surfaceFollow #rimfire 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/rimfire