#164_bvg
Live, measured metrics for the hashtag #164_bvg from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #164_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 · mas.to (Mastodon public tags API) · fetched 2026-07-28 19:06 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-28 19:06 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-28 19:06 UTCEverything below is measured over the latest 35 public posts (spanning ~5235 hours).
Posting hours (UTC) — busiest: 14:00
Languages: German (35)
Avg boosts / post: 0.7
Top of the latest posts
21:51 - #Verkehrsunfall Ende: Die Linien #162_BVG und #164_BVG fahren wieder regulär. #BVG #Berlin
21:23 - #Verkehrsunfall: Die Linien #162_BVG und #164_BVG werden in Richtung Richtung S Adlershof?(Otto-Franke-Straße) bzw. S Köpenick (Kaulsdorfer Straße) von Wegedornstraße/Semmelweißstraße bis S Adlershof umgeleitet. #BVG #Berlin
10:09 - #Verkehrsbehinderung Ende: Die Linien #162_BVG, #163_BVG und #164_BVG fahren 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/164_bvg