#tuapse
Live, measured metrics for the hashtag #tuapse from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tuapse
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.online (Mastodon public tags API) · fetched 2026-09-28 21:51 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.online (Mastodon public search API) · fetched 2026-09-28 21:51 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-28 21:51 UTCEverything below is measured over the latest 40 public posts (spanning ~2934 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (34) · German (5)
Avg boosts / post: 1.2
Top of the latest posts
"Good trouble continues!" 🤣🤣 From https://t.me/Pravda_Gerashchenko 🔥 Taking the baton from #Perm and #Tuapse: in #Bashkortostan today, an oil depot "suddenly" caught fire "Good drones" visited an oil refinery near #Ufa. #ukraine #putinis
"New month, same oily Sh."🤣 From https://t.me/pravdaGerashchenko_en #Russian communist volunteers have arrived in #Tuapse for a cleanup. They spoke respectfully about the Armed Forces of #Ukraine. Zero mentions of the war. #ukraine #putini
At the same time, there are reports of an attack on the #Tuapse refinery – according to eyewitnesses, at least two tanks caught fire. ℹ️ In recent weeks, the #Tuapse refinery has been repeatedly subjected to attacks – strikes were recorded
What “tuapse” means
WikipediaTuapse is a town in Krasnodar Krai, Russia, situated on the northeast shore of the Black Sea, south of Gelendzhik and north of Sochi. Population: 61,571 (2021 census); 63,292 (2010 census); 64,238 (2002 census); 63,081 (1989 Soviet census).
“Tuapse” on Wikipedia (CC BY-SA) →#tuapse across platforms
every network with a public tag surfaceFollow #tuapse 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/tuapse