#texvswas
Live, measured metrics for the hashtag #texvswas from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #texvswas
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 · mas.to (Mastodon public tags API) · fetched 2026-08-15 03:14 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-08-15 03:14 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-08-15 03:14 UTCEverything below is measured over the latest 27 public posts (spanning ~2903 hours).
Posting hours (UTC) — busiest: 04:00
Languages: English (27)
Avg boosts / post: 1.3
Top of the latest posts
That’s game @CFB #CFB #SugarBowl #TEXvsWAS #Longhorns #Huskies
Texas really needed that score. Washington just needs a long drive, with or without point to wrap this up. @CFB #CFB #SugarBowl #TEXvsWAS #Longhorns #Huskies
100% a fumble, 100% Washington recovered, 99% game over. @CFB #CFB #SugarBowl #TEXvsWAS #Longhorns #Huskies
#texvswas across platforms
every network with a public tag surfaceFollow #texvswas 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/texvswas