#Crashdata
Live, measured metrics for the hashtag #Crashdata from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #crashdata
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-11-15 14:30 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-11-15 14:30 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-15 14:30 UTCEverything below is measured over the latest 9 public posts (spanning ~32000 hours).
Posting hours (UTC)
Languages: English (9)
Avg boosts / post: 1.1
Top of the latest posts
Las Vegas! #rstats #shapefile #crashdata
#Tesla was found partly liable in a #wrongfuldeath #lawsuit after a #hacker recovered #crashdata from a 2019 incident. Tesla claimed it didn’t have the data, but the hacker retrieved it from the car’s local storage. Tesla later acknowledged
"For a company that markets its cars as computers on wheels, Tesla’s claim that it had no data available in all these cases is surprising." https://www.theguardian.com/technology/2025/jul/05/the-vehicle-suddenly-accelerated-with-our-baby-in
#crashdata across platforms
every network with a public tag surfaceFollow #crashdata 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/crashdata