#Edomsharde
Live, measured metrics for the hashtag #Edomsharde from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #edomsharde
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-09-28 19:32 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-09-28 19:32 UTCNo related tags with measured usage found for #edomsharde.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-09-28 19:32 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: German (1)
Avg boosts / post: 0
Top of the latest posts
#Edomsharde #Strand #Marcellusflut #Buchardiflut #Rungholt #Archäologie #Nordfriesland #Watt https://www.shz.de/deutschland-welt/schleswig-holstein/artikel/hier-lag-rungholt-die-spannende-suche-der-archaeologen-im-watt-47202590 https://www.
What “edomsharde” means
WikipediaEdoms Hundred was a mediaeval hundred located in the southern part of North Frisia in the Danish region of Southern Schleswig, part of the Frisian Uthlande. It encompassed the eastern part of the island of Strand, which sank in 1634 during the Burchardi flood, including some of the land which now comprises the peninsula of Nordstrand. Edoms Hundred bordered the other so-called Five Hundreds or Strand Hundreds on the island: Beltring Hundred to the north, Pellworm Hundred to the west, Southern Go
“Edoms Hundred” on Wikipedia (CC BY-SA) →#edomsharde across platforms
every network with a public tag surfaceFollow #edomsharde 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/edomsharde