#blogbericht
Live, measured metrics for the hashtag #blogbericht from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #blogbericht
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-10-08 19:52 UTC2 uses by 2 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-10-08 19:52 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-08 19:52 UTCEverything below is measured over the latest 9 public posts (spanning ~1353 hours).
Posting hours (UTC)
Languages: Dutch (9)
Avg boosts / post: 0
Top of the latest posts
#Blogbericht: Giga #Reparatie #DHZ Gesneuvelde #Muis https://ximaar.wordpress.com/2026/10/03/okt-03-giga-reparatie/
#Blogbericht: Rondom #Reuzezwam-men #Alkmaar #DeHout https://ximaar.wordpress.com/2026/09/30/sep-30-rondom-reuzezwammen/
#Blogbericht PopUp Instrument #Alkmaar #Binnenstad #Trillingen https://ximaar.wordpress.com/2026/09/26/sep-26-pop-up-instrument/
#blogbericht across platforms
every network with a public tag surfaceFollow #blogbericht 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/blogbericht