#Gleisbereich
Live, measured metrics for the hashtag #Gleisbereich from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #gleisbereich
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.social (Mastodon public tags API) · fetched 2026-10-07 03:05 UTC2 uses by 2 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-07 03:05 UTCNo related tags with measured usage found for #gleisbereich.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-07 03:05 UTCEverything below is measured over the latest 40 public posts (spanning ~31840 hours).
Posting hours (UTC) — busiest: 13:00
Languages: German (40)
Avg boosts / post: 1.2
Top of the latest posts
Mann springt Kopfhörern in den Gleisbereich hinterher #Bundespolizei #Gleisbereich #Hamburg #SBahn #Station https://bahnblogstelle.com/224741/mann-springt-kopfhoerern-in-den-gleisbereich-hinterher/
Schlägerei im Gleisbereich - Mehrere Verletzte und Festnahmen #Bayern #Bundespolizei #Gewalt #Gleisbereich #Körperverletzung #München #Schlägerei https://bahnblogstelle.com/246645/schlaegerei-im-gleisbereich-mehrere-verletzte-und-festnahmen
Bundespolizei rettet verletzte Taube vor Zug und weitere Blaulichtmeldungen #Aachen #Bahnhof #Bayern #Bundespolizei #Gleisbereich #Gleisläufer #Meiningen #München #Tierrettung https://bahnblogstelle.com/243103/bundespolizei-rettet-verletzte
#gleisbereich across platforms
every network with a public tag surfaceFollow #gleisbereich straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/gleisbereich