#Hengsteysee
Live, measured metrics for the hashtag #Hengsteysee from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hengsteysee
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-10-23 18: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-10-23 18:09 UTCNo related tags with measured usage found for #hengsteysee.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-23 18:09 UTCEverything below is measured over the latest 12 public posts (spanning ~31729 hours).
Posting hours (UTC) — busiest: 06:00
Languages: German (8) · English (1)
Avg boosts / post: 1.7
Top of the latest posts
@FotoVorschlag 'Vom Weg abgekommen' ist auch der Mäuseturm im #Hengsteysee, 2009. #FotoVorschlag #photography #ruhr
Am #Ruhrradweg am #Hengsteysee wird wieder/weiter gebaut. Man soll aber weiterhin dort fahren können: https://www.hagen.de/hagen-aktuell/aktuelle-meldungen/qualifizierung-des-ruhrtalradweges-erster-bauabschnitt-beginnt-40768.html Wir sind g
Das einst beliebte Ausflugs- und Erhohlungziel #Hengsteysee wird durch die #IGA27 ziemlich unattraktiv. So Baut die @Stadt_Hagen 500 neue Autoparkplätze. Ich kann den Frust der Aktiven im @vcdnrw vollauf nachvollziehen. https://nrw.vcd.org/
What “hengsteysee” means
WikipediaThe Hengsteysee is a reservoir on the Ruhr river between the cities of Hagen, Dortmund and Herdecke, North Rhine-Westphalia, Germany. It was built in 1929 and is one of five reservoirs on the Ruhr.
“Hengsteysee” on Wikipedia (CC BY-SA) →#hengsteysee across platforms
every network with a public tag surfaceFollow #hengsteysee 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/hengsteysee