#134_bvg
Live, measured metrics for the hashtag #134_bvg from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #134_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-29 16:27 UTC1 uses by 1 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-29 16:27 UTCNo related tags with measured usage found for #134_bvg.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 16:27 UTCEverything below is measured over the latest 40 public posts (spanning ~3939 hours).
Posting hours (UTC) — busiest: 10:00
Languages: German (40)
Avg boosts / post: 0
Top of the latest posts
12:49 - #Verkehrsunfall Ende: Die Linien #M36_BVG, #M45_BVG, #X36_BVG, #134_BVG und #136_BVG fahren wieder regulär. #BVG #Berlin
12:10 - #Verkehrsunfall: Die Linien #M36_BVG, #M45_BVG, #X36_BVG, #134_BVG und #136_BVG werden in Richtung S+U Rathaus Spandau von Klinkum Spandau (X36) bzw. Kirchhofstraße (136) bzw. Predigergarten (M45) bzw. Falkenhagener Tor (134) bis S+
15:19 - #Feuerwehreinsatz Ende: Die Linie #134_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/134_bvg