#railaccidentsandincidents
Live, measured metrics for the hashtag #railaccidentsandincidents from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #railaccidentsandincidents
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-11-11 06:27 UTC1 uses by 1 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-11-11 06:27 UTCNo related tags with measured usage found for #railaccidentsandincidents.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-11-11 06:27 UTCEverything below is measured over the latest 9 public posts (spanning ~1974 hours).
Posting hours (UTC)
Languages: English (9)
Avg boosts / post: 0
Top of the latest posts
Upgrade for deadly level crossing closer after decades of failed promises By Ellen-Maree Elliot A deadly level railway crossing is closer to a major upgrade as another junction just suburbs away on a key rail corridor runs out of steam. htt
Spain begins three days of mourning as train crash death toll reaches 69 Spain has begun three days of mourning after its second high-speed rail collision this year killed 69 people. https://www.abc.net.au/news/2026-10-30/brk-spain-train-up
Conflicting accounts emerge after Spanish train collision By Maddie Nixon Contradictions have emerged between a private rail operator and the Spanish government over what caused Europe's deadliest train collision since 2013, according to lo
#railaccidentsandincidents across platforms
every network with a public tag surfaceFollow #railaccidentsandincidents 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/railaccidentsandincidents