#killteam24
Live, measured metrics for the hashtag #killteam24 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #killteam24
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-27 23:04 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-27 23:04 UTCNo related tags with measured usage found for #killteam24.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 23:04 UTCEverything below is measured over the latest 12 public posts (spanning ~1456 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (12)
Avg boosts / post: 0.9
Top of the latest posts
Turning point two down, I’ve lost a sicaran, my ranger prime and my diktat to the withering gunfire from the mage hunters. Fortunately the imperial militia reinforcements were swiftly dashed. Unfortunately theyre sound of pissed off fascist
The Ratmech stumbled on a significant cache of archeotech and cheese. Unfortunately in their rush to collect the goodies they alerted a nearby patrol of Mage Hunters. Each turning point a new NPO kill team will enter from a randomly determi
Getting back into the campaign tonight. Skipped through some non combat turns and got to this whopping mess. 280 wounds of NPO's all converged on my Killteam in sniper alley. Narratively this has to be some kind of column that I've stumbled
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/killteam24