#oostakker
Live, measured metrics for the hashtag #oostakker from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #oostakker
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-09-27 13:00 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.online (Mastodon public search API) · fetched 2026-09-27 13:00 UTCNo related tags with measured usage found for #oostakker.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-27 13:00 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: Dutch (1)
Avg boosts / post: 1
Used together with
Top of the latest posts
Op 1 maand is het aantal #MeshCore repeaters in stedelijk Gent gestegen van 9 naar 13. Regio Gent zelfs 19 met repeaters in #Landegem, #Drongen, #Oostakker, #Lochristi en #Laarne. En er zitten nog installaties in de pipeline...
What “oostakker” means
WikipediaOostakker is a sub-municipality of the city of Ghent located in the province of East Flanders, Flemish Region, Belgium. It was a separate municipality until 1977. In 1872, Sint-Amandsberg was detached from Oostakker. In 1900, 1920 and 1927, parts of the original municipality were already annexed to Ghent. On 1 January 1977, the municipality of Oostakker was merged into Ghent.
“Oostakker” on Wikipedia (CC BY-SA) →#oostakker across platforms
every network with a public tag surfaceFollow #oostakker 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/oostakker