#248_bvg
Live, measured metrics for the hashtag #248_bvg from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #248_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 20:24 UTC6 uses by 3 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 20:24 UTCNo related tags with measured usage found for #248_bvg.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 20:24 UTCEverything below is measured over the latest 40 public posts (spanning ~2721 hours).
Posting hours (UTC) — busiest: 05:00
Languages: German (40)
Avg boosts / post: 0
Top of the latest posts
17:01 - #Verkehrsunfall Ende: Die Linien #140_BVG und #248_BVG fahren wieder regulär. #BVG #Berlin
16:45 - #Verkehrsunfall: Die Linie #140_BVG wird zwischen Blücherstraße und U Mehringdamm umgeleitet. Die Linie #248_BVG wird zwischen Kaiserkorso und U Hallesches Tor umgeleitet. #BVG #Berlin
11:56 - #Verkehrsunfall Ende: Die Linien #M41_BVG und #248_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/248_bvg