#CreekFire
Live, measured metrics for the hashtag #CreekFire from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #creekfire
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-10-04 21:02 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-10-04 21:02 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-04 21:02 UTCEverything below is measured over the latest 40 public posts (spanning ~13916 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (40)
Avg boosts / post: 1.8
Top of the latest posts
No updates since the original post on watch duty 17 hrs ago. I hope that’s good news, but would be nice to have some confirmation. #CreekFire
This new #CreekFire is in a scary location for camp. Hope they get on it fast.
#NIFC #wildfires #firewx NIFC New Or Updated Wildfire Perimeter Incident Name: Creek Acres: 3.3 acres Updated: Jul 12, 2026 16:38 UTC Source: IRWIN #CreekFire #MNwx
#creekfire across platforms
every network with a public tag surfaceFollow #creekfire 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/creekfire