#Route3
Live, measured metrics for the hashtag #Route3 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #route3
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-11-06 02:27 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-11-06 02:27 UTCNo related tags with measured usage found for #route3.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-11-06 02:27 UTCEverything below is measured over the latest 30 public posts (spanning ~41034 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (29) · German (1)
Avg boosts / post: 5.9
Top of the latest posts
Hype for the Future 236F: Wooster, Ohio Overview The City of Wooster is a notable mid-sized city west of Canton within the east-central portion of the State of Ohio that serves as the county seat of modern Wayne County, Ohio, home to the Co
Hype for the Future 234A: Sunbury, Ohio Overview The City of Sunbury is a small city located in the eastern portion of Delaware County in the State of Ohio along Routes 36, 3, 37, and 61 and associated with the Old Sunbury Courthouse, the M
Hype for the Future 232A: Fayette County, Ohio Overview Fayette County is a notable county located in the southwestern portion of a region known as Central Ohio which uses the City of Washington Court House as the county seat and is home to
What “route3” means
Wiktionaryroute/ɹʉːt/
- nounA course or way which is traveled or passed.
- verbTo direct or divert along a particular course.
#route3 across platforms
every network with a public tag surfaceFollow #route3 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/route3