#medewerker
Live, measured metrics for the hashtag #medewerker from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #medewerker
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-08-03 01:10 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-08-03 01:10 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-03 01:10 UTCEverything below is measured over the latest 14 public posts (spanning ~26267 hours).
Posting hours (UTC) — busiest: 08:00
Languages: Dutch (9) · English (5)
Avg boosts / post: 0.2
Top of the latest posts
𝗡𝗮𝗮𝘀𝘁𝗲 𝗺𝗲𝗱𝗲𝘄𝗲𝗿𝗸𝗲𝗿 '𝘃𝗲𝗿𝗱𝗶𝗲𝗻𝗱𝗲 𝗴𝗲𝗹𝗱 𝗱𝗼𝗼𝗿 𝗴𝗼𝗸𝗸𝗲𝗻 𝗼𝗽 𝘂𝗶𝘁𝘀𝗽𝗿𝗮𝗸𝗲𝗻 𝗧𝗿𝘂𝗺𝗽' Een medewerker van het Witte Huis wordt onderzocht omdat hij mogelijk voorkennis gebruikte om te gokken op toespraken
𝗠𝗲𝗱𝗲𝘄𝗲𝗿𝗸𝗲𝗿 𝘇𝗲𝗴𝘁 𝘁𝗶𝗷𝗱𝗲𝗻𝘀 𝗽𝗲𝗿𝘀𝗰𝗼𝗻𝗳𝗲𝗿𝗲𝗻𝘁𝗶𝗲 𝘁𝗲𝗴𝗲𝗻 𝗰𝗼𝗮𝗰𝗵 𝗖𝗼𝗻𝗴𝗼 𝗱𝗮𝘁 𝘃𝗮𝗱𝗲𝗿 𝗶𝘀 𝗼𝘃𝗲𝗿𝗹𝗲𝗱𝗲𝗻 Een opvallend moment tijdens de persconferentie na afloop van de WK-wedstrijd tussen Enge
𝗠𝗲𝗱𝗲𝘄𝗲𝗿𝗸𝗲𝗿 𝗴𝗼𝘂𝗱𝘄𝗶𝘀𝘀𝗲𝗹𝗸𝗮𝗻𝘁𝗼𝗼𝗿 𝗕𝗲𝘃𝗲𝗿𝘄𝗶𝗷𝗸 𝗼𝘃𝗲𝗿𝗹𝗲𝗱𝗲𝗻 𝗻𝗮 𝗼𝘃𝗲𝗿𝘃𝗮𝗹 Door de gewelddadige overval op een goudwisselkantoor in Beverwijk gisteren is een medewerker om het leven gekomen. De politie
#medewerker across platforms
every network with a public tag surfaceFollow #medewerker 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/medewerker