#hesperiafire
Live, measured metrics for the hashtag #hesperiafire from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hesperiafire
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-07-31 03:09 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-07-31 03:09 UTCNo related tags with measured usage found for #hesperiafire.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-31 03:09 UTCEverything below is measured over the latest 3 public posts (spanning ~12 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.3
Used together with
Top of the latest posts
#HesperiaFire - Hesperia, San Bernardino County 1,330 acres, 7% contained #Postfire - #Gorman, Los Angeles County 11,000 acres, 0% contained (06/16/24 -7 am)
#HesperiaFire > Hesperia, San Bernardino County started by firework #Postfire > Gorman, Los Angeles County = vehicle fire in to dry vegetation
#HesperiaFire > Hwy 173 & Arrowhead Lake Rd, Hesperia, San Bernardino County, CA {40 acres} Watch Duty > https://app.watchduty.org/#/i/21998 Cam > https://ops.alertcalifornia.org/cam-console/1912
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/hesperiafire