#Route163
Live, measured metrics for the hashtag #Route163 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #route163
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-09-05 13:20 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-09-05 13:20 UTCNo related tags with measured usage found for #route163.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-05 13:20 UTCEverything below is measured over the latest 3 public posts (spanning ~571 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 11
Top of the latest posts
Hype for the Future 219H: City of Clinton, Indiana Overview The City of Clinton is a notable community located within the boundaries of Vermillion County, Indiana, home to Gerrie’s Italian on 9th Street and the Co-Op Grill within the west-c
Hype for the Future 197B: City of Pella, Iowa Overview The City of Pella is a city in and a notable Dutch immigrant settlement of Marion County, Iowa, larger than the county seat at Knoxville to the southwest. Today, the community is associ
Hype for the Future 195E: City of Oskaloosa, Iowa Overview The City of Oskaloosa is a city located within and the county seat of Mahaska County, Iowa, along Routes 63, 23, 92, and 163. Today, the community is located within the southeastern
What “route163” means
Wiktionaryroute/ɹʉːt/
- nounA course or way which is traveled or passed.
- verbTo direct or divert along a particular course.
#route163 across platforms
every network with a public tag surfaceFollow #route163 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/route163