#havelkanal
Live, measured metrics for the hashtag #havelkanal from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #havelkanal
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-10-22 07:12 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-10-22 07:12 UTCNo related tags with measured usage found for #havelkanal.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-22 07:12 UTCEverything below is measured over the latest 2 public posts (spanning ~4.3 hours).
Posting hours (UTC)
Languages: German (2)
Avg boosts / post: 0
Top of the latest posts
Nach rund 22km Ankunft am Etappenort Brieselang - damit haben wir die zweite Etappe geschafft, ingesamt 37 von 419km hinter uns gebracht. Eine matschige Angelegenheit. Mehr Bilder und Infos bei Insta https://www.instagram.com/wanderinode #w
Die ersten 9km sind im Kasten, das Wetter ist schöner geworden und für Februar sehr mild. Unsere Seen sind heute wassergefüllte Senken, Teiche und der Havelkanal. Was Übergangsetappen eben so zu bieten haben. #wanderung #wandern #hiking #ha
What “havelkanal” means
WikipediaThe Havel Canal, or Havelkanal in German, is a canal in the German state of Brandenburg. It provides an alternate route to the River Havel, between Hennigsdorf and Paretz, thus avoiding a passage through the waterways of Berlin between Spandau and Potsdam.
“Havel Canal” on Wikipedia (CC BY-SA) →#havelkanal across platforms
every network with a public tag surfaceFollow #havelkanal 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/havelkanal