#m32_bvg
Live, measured metrics for the hashtag #m32_bvg from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #m32_bvg
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-07-30 16:38 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-07-30 16:38 UTCNo related tags with measured usage found for #m32_bvg.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 16:38 UTCEverything below is measured over the latest 16 public posts (spanning ~3499 hours).
Posting hours (UTC) — busiest: 06:00
Languages: German (16)
Avg boosts / post: 0
Top of the latest posts
8:29 - #Verkehrsunfall Ende: Die Linien #M32_BVG, #X49_BVG und #131_BVG fahren wieder regulär. #BVG #Berlin
8:18 - #Verkehrsunfall: Die Linie #M32_BVG wird in Richtung Havelpark bzw. Brunsbütteler Damm/Stadtgrenze bzw. Heidebergplan von Nauener Straße bis Alt-Staaken Kirche bzw. Eidechsenweg bzw. Heidebergplan umgeleitet. #BVG #Berlin
10:09 - #Verkehrsbehinderung Ende: Die Linie #M32_BVG fährt wieder regulär. #BVG #Berlin
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/m32_bvg