#KanchenjungaTrek
Live, measured metrics for the hashtag #KanchenjungaTrek from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #kanchenjungatrek
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-07 21:46 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-07 21:46 UTCNo related tags with measured usage found for #kanchenjungatrek.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-08-07 21:46 UTCEverything below is measured over the latest 2 public posts (spanning ~21 hours).
Posting hours (UTC)
Avg boosts / post: 0.5
Top of the latest posts
Some treks welcome you with warm rooms, menus, and familiar smiles. Kanchenjunga welcomes you with silence. Day 3: Gyabla to Phale Gau was the day I understood that this trek is not built around tourists. Everest Base Camp trek is crowded,
A small cold in the Himalaya is not always a small thing. Day 2 of the Kanchenjunga trek: Lamatar to Gyabla — around 13 km and about 1,300 m of climbing. I woke up with a sore throat, blocked nose, and a dull headache. Not dramatic at low a
#kanchenjungatrek across platforms
every network with a public tag surfaceFollow #kanchenjungatrek 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/kanchenjungatrek