#stillgelegtebahnstrecke
Live, measured metrics for the hashtag #stillgelegtebahnstrecke from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #stillgelegtebahnstrecke
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-10-29 10:49 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-10-29 10:49 UTCNo related tags with measured usage found for #stillgelegtebahnstrecke.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-29 10:49 UTCEverything below is measured over the latest 20 public posts (spanning ~24130 hours).
Posting hours (UTC) — busiest: 11:00
Languages: German (19)
Avg boosts / post: 1.6
Top of the latest posts
Gleisrückbau ohne Genehmigung - Konflikt um Untere Steigerwaldbahn spitzt sich zu #Bahnstrecke #Bayern #Eisenbahnrecht #Gleisrückbau #Grosslangheim #Infrastruktur #Steigerwaldbahn #Strukturwandel #Unterfranken #Verkehrspolitik #stillgelegte
Allianz pro Schiene: Neuer Schwung bei Reaktivierung alter Bahnstrecken #AllianzproSchiene #Bahnstrecke #Infrastruktur #Reaktivierung #Verkehrspolitik #stillgelegteBahnstrecke https://bahnblogstelle.com/254533/allianz-pro-schiene-neuer-schw
Saftbahn bei Bitterfeld könnte reaktiviert werden #Bahnstrecke #Bitterfeld #Infrastruktur #Köthen #Leipzig #LydiaHüskens #Nasa #ProBahn #Reaktivierung #Saftbahn #Stumsdorf #Zörbig #stillgelegteBahnstrecke https://bahnblogstelle.com/248789/s
#stillgelegtebahnstrecke across platforms
every network with a public tag surfaceFollow #stillgelegtebahnstrecke 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/stillgelegtebahnstrecke