#Route73
Live, measured metrics for the hashtag #Route73 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #route73
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-10-02 18:13 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-10-02 18:13 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-02 18:13 UTCEverything below is measured over the latest 15 public posts (spanning ~2795 hours).
Posting hours (UTC) — busiest: 00:00
Languages: English (15)
Avg boosts / post: 3.1
Top of the latest posts
Hype for the Future 229B: Cincinnati East (Rural) Introduction Notable counties located east of Cincinnati, though in the same media market, include Brown, Adams, Highland, and Clinton Counties and are associated with significantly smaller
Hype for the Future 229A: Greater Cincinnati, Ohio Introduction Greater Cincinnati is largely associated with a tristate area of Ohio, Kentucky, and Indiana, with numerous counties in the southwestern portion of Ohio and Northern Kentucky l
Hype for the Future 228F: Village of Waynesville, Ohio Overview The Village of Waynesville is a notable village located within the northeastern portion of Warren County, Ohio, home to the Museum at the Friends Home, the Canada Goose Gallery
What “route73” means
Wiktionaryroute/ɹʉːt/
- nounA course or way which is traveled or passed.
- verbTo direct or divert along a particular course.
#route73 across platforms
every network with a public tag surfaceFollow #route73 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/route73