#x83_bvg
Live, measured metrics for the hashtag #x83_bvg from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #x83_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-27 06:33 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-27 06:33 UTCNo related tags with measured usage found for #x83_bvg.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 06:33 UTCEverything below is measured over the latest 24 public posts (spanning ~3923 hours).
Posting hours (UTC) — busiest: 14:00
Languages: German (24)
Avg boosts / post: 0
Top of the latest posts
20:13 - #Feuerwehreinsatz Ende: Die Linie #X83_BVG fährt wieder regulär. #BVG #Berlin
19:43 - #Feuerwehreinsatz: Die Linie #X83_BVG wird zwischen Lankwitz Kirche und Friedenfelser Straße umgeleitet. #BVG #Berlin
19:58 - #Verkehrsunfall Ende: Die Linie #X83_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/x83_bvg