#oopse
Live, measured metrics for the hashtag #oopse from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #oopse
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-12 05:42 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-12 05:42 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-12 05:42 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
It took 22 overs for India to beat Afghanistan in their T20 on Wednesday night. How? Watch the match highlights: https://www.bcci.tv/bccilink/videos/fYoJDqGf #cricket #IndvAfg #OOPSE
What “oopse” means
WikipediaSuper Over, also known as a one-over eliminator or a one over per side eliminator, is a tie-breaking method used in limited-overs cricket matches similar to overtime in most other sports and extra innings in baseball. If a match ends in a "tie", it proceeds to a Super Over, in which each team plays a single additional over of six balls to determine the winner. The team scoring the most runs in that over is declared the winner.
“Super Over” on Wikipedia (CC BY-SA) →#oopse across platforms
every network with a public tag surfaceFollow #oopse 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/oopse