#ThreeJourneysNorth
Live, measured metrics for the hashtag #ThreeJourneysNorth from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #threejourneysnorth
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.social (Mastodon public tags API) · fetched 2026-09-26 00:40 UTC12 uses by 6 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-09-26 00:40 UTCNo related tags with measured usage found for #threejourneysnorth.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-26 00:40 UTCEverything below is measured over the latest 40 public posts (spanning ~460 hours).
Posting hours (UTC) — busiest: 23:00
Languages: English (40)
Avg boosts / post: 0.1
Top of the latest posts
NO ORDINARY RISKS: EXPLORATIONS FROM HUDSON BAY TO THE ARCTIC SEA At Cumberland House, the HBC men who were travelling North left the #Saskatchewan River and began their journey up the rapid-filled Sturgeon-Weir. #Journeys #ThreeJourneysNor
NO ORDINARY RISKS: EXPLORATIONS FROM HUDSON BAY TO THE ARCTIC SEA James Anderson, Chief Factor in charge of the Mackenzie river district, made notes that give us details of the river and overland route from Fort Simpson all the way to the P
NO ORDINARY RISKS: EXPLORATIONS FROM HUDSON BAY TO THE ARCTIC SEA In 1847, clerk Augustus Richard Peers left Fort Norman and took over the charge of a more Northerly post called the Peel's River Post. Here he tells the story of his journey
#threejourneysnorth across platforms
every network with a public tag surfaceFollow #threejourneysnorth 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/threejourneysnorth