#ongelukklimhal
Live, measured metrics for the hashtag #ongelukklimhal from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ongelukklimhal
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-10-15 04:34 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-10-15 04:34 UTCNo related tags with measured usage found for #ongelukklimhal.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-15 04:34 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: Dutch (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
𝗠𝗮𝗻 (33) 𝘇𝘄𝗮𝗮𝗿𝗴𝗲𝘄𝗼𝗻𝗱 𝗯𝗶𝗷 𝗼𝗻𝗴𝗲𝗹𝘂𝗸 𝗶𝗻 𝗸𝗹𝗶𝗺𝗵𝗮𝗹 𝗔𝗿𝗻𝗵𝗲𝗺 Bij een ongeluk in een klimhal in Arnhem is vandaag een 33-jarige man zeker zes meter naar beneden gevallen. Hij is zwaargewond, maar wel aanspreekbaa
#ongelukklimhal across platforms
every network with a public tag surfaceFollow #ongelukklimhal 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/ongelukklimhal