#160_BVG
Live, measured metrics for the hashtag #160_BVG from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #160_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 · mastodon.online (Mastodon public tags API) · fetched 2026-07-28 23:51 UTC2 uses by 1 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-07-28 23:51 UTCNo related tags with measured usage found for #160_bvg.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-28 23:51 UTCEverything below is measured over the latest 27 public posts (spanning ~5312 hours).
Posting hours (UTC) — busiest: 06:00
Languages: German (27)
Avg boosts / post: 0.8
Top of the latest posts
18:30 - #Feuerwehreinsatz Ende: Die Tramlinien #M17_BVG, #37_BVG, #60_BVG, #63_BVG und #67_BVG, sowie die Buslinie #160_BVG fahren wieder planmäßig. #BVG #Berlin
16:58 - #Feuerwehreinsatz: Die Linie #160_BVG fährt nicht zwischen S Schöneweide/Sterndamm und Hasselwerderstraße. #BVG #Berlin
13:09 - #Feuerwehreinsatz Ende: Die Linien #160_BVG und #165_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/160_bvg