#stellwerksstörung
Live, measured metrics for the hashtag #stellwerksstörung from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #stellwerksstorung
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-08-06 10:05 UTC0 uses by 0 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-08-06 10:05 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-08-06 10:05 UTCEverything below is measured over the latest 17 public posts (spanning ~33731 hours).
Posting hours (UTC) — busiest: 04:00
Languages: German (17)
Avg boosts / post: 0.6
Top of the latest posts
Und los gehts mit dem Rahmenprogramm der Generalversammlung der @glsbank Ich habe es trotz #signalstörung und #stellwerksstörung der #bahn geschafft in Bochum anzukommen. #gls
* Nachdem das Problem mit der Klappe gelöst war, noch zwei Stunden an einem winzigen Bahnhof in der mittelhessischen Pampa rumgestanden wegen #Stellwerksstörung in #Kassel. Offenbar konnten dutzende ICEs nicht weiterfahren und stauten sich
Verdacht auf Brandstiftung: Feuer an Signalkabeln bei Kassel #Brand #Brandstiftung #Hessen #Kabelschaden #Kassel #NVV #Polizei #Signalkabel #Stellwerksstörung https://bahnblogstelle.com/233355/verdacht-auf-brandstiftung-feuer-an-signalkabel
#stellwerksstorung across platforms
every network with a public tag surfaceFollow #stellwerksstorung 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/stellwerksstorung