#zugentgleisung
Live, measured metrics for the hashtag #zugentgleisung from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #zugentgleisung
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.online (Mastodon public tags API) · fetched 2026-10-30 01:00 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.online (Mastodon public search API) · fetched 2026-10-30 01:00 UTCNo related tags with measured usage found for #zugentgleisung.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-30 01:00 UTCEverything below is measured over the latest 40 public posts (spanning ~31288 hours).
Posting hours (UTC) — busiest: 09:00
Languages: German (40)
Avg boosts / post: 0.9
Top of the latest posts
Untersuchungsbericht über Zugentgleisung am 03.06.2022 in Garmisch‐Partenkirchen - Farchant https://www.eisenbahn-unfalluntersuchung.de/SharedDocs/Downloads/BEU/Untersuchungsberichte/2022/231_Garmisch-Partenkirchen-_-Farchant.html #Zugentgl
Untersuchungsbericht über Zugentgleisung am 23.02.2022 in Rüsselsheim https://www.eisenbahn-unfalluntersuchung.de/SharedDocs/Downloads/BEU/Untersuchungsberichte/2022/220_Ruesselsheim.html #Zugentgleisung #BahnBubble #ZugBubble #BEU #Unfall
Zwischenbericht über Zugentgleisung am 06.12.2022 in Saarbrücken Rbf https://www.eisenbahn-unfalluntersuchung.de/SharedDocs/Downloads/EUB/Zwischenberichte/2022/90_Zwischenbericht_Saarbruecken.html #Zugentgleisung #BahnBubble #ZugBubble #BEU
#zugentgleisung across platforms
every network with a public tag surfaceFollow #zugentgleisung 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/zugentgleisung