#hallingskeid
Live, measured metrics for the hashtag #hallingskeid from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hallingskeid
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-10-22 13:33 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-10-22 13:33 UTCNo related tags with measured usage found for #hallingskeid.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-22 13:33 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: Norwegian Bokmål (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
@olemd Men vent litt, er det det nye snøoverbygget i aluminium o.l. som det har vært brann i? Det er vel ingen vits å spørre #Sørlandsbanen-folk som @nilshenrik? En skulle ikke tro at en bane til/fra Bergen brenner så lett. #Bergensbanen #H
What “hallingskeid” means
WikipediaHallingskeid Station is a train station on the Bergen Line in Ulvik Municipality in Vestland county, Norway. Located at an elevation of 1,110 meters (3,640 ft) above mean sea level, the station is situated inside a snow tunnel. It opened along with the central section of the line on 10 June 1908 and remained as a staffed station until 1982. It is located on the Hardangervidda plateau in an area without population or road access. The station therefore serves trekkers and mountaineers. Only some o
“Hallingskeid Station” on Wikipedia (CC BY-SA) →#hallingskeid across platforms
every network with a public tag surfaceFollow #hallingskeid 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/hallingskeid