#setesdalsbanen
Live, measured metrics for the hashtag #setesdalsbanen from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #setesdalsbanen
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-27 16:07 UTCNo measured public usage for #setesdalsbanen in the last 7 days. That is a real result, and a good one to know: this hashtag is wide open right now. We show a dash before we ever show a made-up number. Browse the trending index for tags with live measurements.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-09-27 16:07 UTCNo related tags with measured usage found for #setesdalsbanen.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-27 16:07 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Avg boosts / post: 2
Used together with
No co-used tags in the sample.
Top of the latest posts
My last Norwegian narrow gauge railway: 1067 mm Setesdalsbanen from Vennesla up to Røyknes goes through a scenic valley of the river Otra. You can walk 6 km on track and return through a trough that once served for flowing woods. Moje posle
What “setesdalsbanen” means
WikipediaThe Setesdal Line was a railway between Kristiansand and Byglandsfjord in southern Norway, 78 km (48 mi) long. It was built with a narrow gauge of 1,067 mm, and opened to Hægeland 26 November 1895, and to Byglandsfjord 27 November 1896. Stations along the line included Mosby, Vennesla, Grovene (Grovane), Iveland and Hægeland.
“Setesdal Line” on Wikipedia (CC BY-SA) →#setesdalsbanen across platforms
every network with a public tag surfaceFollow #setesdalsbanen 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/setesdalsbanen