#traincrash
Live, measured metrics for the hashtag #traincrash from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #traincrash
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-07-27 22:52 UTC0 uses by 0 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-07-27 22:52 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:52 UTCEverything below is measured over the latest 40 public posts (spanning ~28829 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (36) · Portuguese (2) · German (2)
Avg boosts / post: 1.6
Top of the latest posts
Yesterday there was a horrible train crash near Bedford. The driver of one of the trains died, many passengers were injured. The cause is not known. Without minimising this for the victims, let's not forget that this was only the fourth dea
Getting back home yesterday took so long because of the train crash which happened near Bedford. But, I got to come home, unlike the poor driver involved in the crash. #TrainCrash
Today's report from the "Rail Accident Investigation Branch" (RAIB), explaining what's known so far about the crash last week. https://www.gov.uk/government/news/collision-between-two-passenger-trains-near-elstow If I understand correctly,
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/traincrash