#odishatrainaccident
Live, measured metrics for the hashtag #odishatrainaccident from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #odishatrainaccident
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-08-02 13:34 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-08-02 13:34 UTCNo related tags with measured usage found for #odishatrainaccident.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-02 13:34 UTCEverything below is measured over the latest 13 public posts (spanning ~747 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (13)
Avg boosts / post: 0.6
Top of the latest posts
Long, Difficult Process Of Identifying The Dead Prolongs Grief & Horror For Odisha Train-Crash Families A month after a three-train wreck in Balasore, Odisha, killed over 290 people on 2 June, 52 bodies are yet to be identified. As mostly l
Modi government’s special fund for railway safety spent on foot massagers, crockery, winter jackets: CAG report This spending sleight of hand and the sharp rap that the government auditors delivered to the railway czars may never have becom
Electrocution Likely Behind 40 Deaths In Balasore Train Accident: Railway Police An FIR registered at the Government Railway Police station at Balasore indicated that live overhead wires which snapped when the accident occurred, entangled w
#odishatrainaccident across platforms
every network with a public tag surfaceFollow #odishatrainaccident 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/odishatrainaccident