#brandenburgodyssee
Live, measured metrics for the hashtag #brandenburgodyssee from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #brandenburgodyssee
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-08-01 15:43 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-08-01 15:43 UTCNo related tags with measured usage found for #brandenburgodyssee.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-01 15:43 UTCEverything below is measured over the latest 8 public posts (spanning ~3018 hours).
Posting hours (UTC)
Languages: English (4) · German (4)
Avg boosts / post: 0.8
Top of the latest posts
Especially tiring were the last 20km towards Fürdenwalde. I somehow thought I finished the hard part as there were no more mountains. But it was extremely sandy and I was sneaking along with something around 10-15km/h. @fedibikes_berlin #bi
@fedibikes_berlin Now I've finished the 218 km of the first section (of the ~1300km route). Took me 3 day trips over 6 weeks. The greenery in May definitely gives for a nicer ride experience. The first section is noted on the webpage to be
Wochenrückblick, Ausgabe 86 (2025-14) Themen: 🖥️ Dachbodenfund: iMac aus 2006 🗺️ Bikerouter-Kleinigkeiten und Wechsel des Domain-Registrars 🐙 Gekündigt: mein bezahltes GitHub-Abo 👨💻 Awesome Gitea: Liste mit allerlei interessantem Zeug
#brandenburgodyssee across platforms
every network with a public tag surfaceFollow #brandenburgodyssee 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/brandenburgodyssee