#industrialaccident
Live, measured metrics for the hashtag #industrialaccident from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #industrialaccident
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-10-05 04:53 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-10-05 04:53 UTCNo related tags with measured usage found for #industrialaccident.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-05 04:53 UTCEverything below is measured over the latest 40 public posts (spanning ~24272 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (37) · Hindi (1) · French (1)
Avg boosts / post: 0.2
Top of the latest posts
Catastrophic explosion at lumber plant in rural #Maine finds regional hospitals overwhelmed and unable to care for critically wounded employees. https://www.the-independent.com/news/world/americas/maine-mass-casualty-incident-lumber-yard-ex
🟡 Industrial Accident | 7/10 🇨🇳 Fireworks factory explosion in China — 21 killed A massive explosion occurred at a fireworks factory in Liuyang, Hunan Province, China. At least 21 people have been killed as a result of the incident. Addi
Man dies in industrial accident after falling into silo in Liverpool factory A tragic industrial accident occurred on Monday evening in Liverpool when a 45-year-old man fell into an empty silo at a factory on Woodend Avenue in Speke. Emerge
#industrialaccident across platforms
every network with a public tag surfaceFollow #industrialaccident 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/industrialaccident