#doornspijk
Live, measured metrics for the hashtag #doornspijk from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #doornspijk
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.social (Mastodon public tags API) · fetched 2026-09-25 21:02 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.social (Mastodon public search API) · fetched 2026-09-25 21:02 UTCNo related tags with measured usage found for #doornspijk.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-25 21:02 UTCEverything below is measured over the latest 9 public posts (spanning ~15128 hours).
Posting hours (UTC)
Languages: English (7) · Dutch (2)
Avg boosts / post: 0
Top of the latest posts
Yesterday I was in Elburg where I'd never been. Very touristy but deservedly so, even on a clouded day. It was at the end of a 21 km walk so I wasn't really up for sightseeing, maybe another time. Still, some photos. https://nl.wikipedia.or
🚨🚁: Traumaheli (Amsterdam-Amstelland) met Prio 1 naar melding: "Traumaheli persoon in levensgevaar" op Schootbruggeweg te Doornspijk (Noord-Holland). 𝗣𝟮𝟬𝟬𝟬: A1 (DIA) 13991 Schootbruggeweg 8085 Doornspijk 88122 regio 06 𝗥𝗲𝗴𝗶𝗼: Am
🚨🚁: Traumaheli (Amsterdam-Amstelland) met Prio 1 naar melding: "Traumaheli persoon in levensgevaar" op Zuiderzeestraatweg West te Doornspijk (Noord-Holland). 𝗣𝟮𝟬𝟬𝟬: A1 (DIA) 13991 Zuiderzeestraatweg West 8085 Doornspijk 73373 regio 0
What “doornspijk” means
WikipediaDoornspijk is a village in the Dutch province of Gelderland. It is located in the municipality of Elburg.
“Doornspijk” on Wikipedia (CC BY-SA) →#doornspijk across platforms
every network with a public tag surfaceFollow #doornspijk 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/doornspijk