#Kavkaz
Live, measured metrics for the hashtag #Kavkaz from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #kavkaz
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 · mastodon.social (Mastodon public tags API) · fetched 2026-09-26 02:57 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-09-26 02:57 UTCNo related tags with measured usage found for #kavkaz.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-26 02:57 UTCEverything below is measured over the latest 33 public posts (spanning ~26156 hours).
Posting hours (UTC) — busiest: 01:00
Languages: English (30) · Russian (2) · German (1)
Avg boosts / post: 1.5
Top of the latest posts
🧵 The burning ferry "Conro Trader" loaded with fuel in the port of #Kavkaz, #Krasnodar region, #Russia after being hit by #Ukraine according to local authorities. The ferry was carrying 30 fuel tanks. https://t.me/Crimeanwind/65980
6/ Aftermath https://t.me/ssternenko/32741 #Ukraine #Russia #Kavkaz
4/ Ferry before the attack https://t.me/Crimeanwind/65987 #Ukraine #Russia #Kavkaz
#kavkaz across platforms
every network with a public tag surfaceFollow #kavkaz 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/kavkaz