#øyeren
Live, measured metrics for the hashtag #øyeren from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #oyeren
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-25 19:27 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-25 19:27 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-25 19:27 UTCEverything below is measured over the latest 24 public posts (spanning ~28254 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (11)
Avg boosts / post: 0.9
Top of the latest posts
#norge #norway #kajakk #kayaking #onthebeach #onthemove #nature #river #elv #glomma #øyeren
Spasertur på vannet på Fetsund Lenser/Walking on water (almost) at Fetsund lenser (note: no alligators in Norwegian wetlands), 29. september 2024 #høst2024 #autumn2024 #september2024 #høst #autumn #fetsund #fetsund_lenser #våtmark #wetlands
Fugletårnet på Årnestangen, med en lang plankesti utover, Rælingsøya, Rælingen 2. november 2025 #autumn2025 #høst2025 #november2025 #autumn #høst #elevatedWalkway #walkway #plankesti #fugletårn #årnestangenFugletårn #nordreØyernNaturreserva
What “oyeren” means
WikipediaØyeren is a lake in the Glomma River watershed, southeast of the city of Lillestrøm. It is located within the municipalities of Enebakk, Lillestrøm, and Rælingen in Akershus county and Indre Østfold municipality in Østfold county.
“Øyeren” on Wikipedia (CC BY-SA) →#oyeren across platforms
every network with a public tag surfaceFollow #oyeren 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/oyeren