#gloppefjord
Live, measured metrics for the hashtag #gloppefjord from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #gloppefjord
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.online (Mastodon public tags API) · fetched 2026-09-26 11:38 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-09-26 11:38 UTCNo related tags with measured usage found for #gloppefjord.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-26 11:38 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0
Top of the latest posts
Now It Has Been Confirmed: – The Largest Burial Mound In Western Norway https://riksantikvaren.no/na-er-det-bekreftet-den-storste-gravhaugen-pa-vestlandet/ <-- shared technical article -- #GIS #spatial #mapping #survey #remotesensing #groun
What “gloppefjord” means
WikipediaGloppefjorden is a fjord in Gloppen Municipality in Vestland county, Norway. The 12-kilometre (7.5 mi) long fjord flows from the village of Sandane in the southeast to its mouth at the Nordfjorden in the northwest. The river Gloppeelva is the primary inflow on the fjord. The river comes from the large lake Breimsvatnet. The 2.7-kilometre (1.7 mi) wide fjord has a lot of settlements along the inner parts of the fjord, especially on the eastern side of the fjord. The most notable village areas are
“Gloppefjorden” on Wikipedia (CC BY-SA) →#gloppefjord across platforms
every network with a public tag surfaceFollow #gloppefjord 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/gloppefjord