#Dinkelsbühl
Live, measured metrics for the hashtag #Dinkelsbühl from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dinkelsbuhl
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-10-15 19:49 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-10-15 19:49 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-15 19:49 UTCEverything below is measured over the latest 40 public posts (spanning ~1443 hours).
Posting hours (UTC) — busiest: 09:00
Languages: German (39)
Avg boosts / post: 0.1
Top of the latest posts
Treppe an der Stadtmauer in Dinkelsbühl 16.03.2026 #blackandwhite #blackandwhitephotography #swfotografie #travelphotography #Travel #Dinkelsbühl #kontraste #reisefotografie
Es regnet. #Wohnmobilstellplatz #Dinkelsbühl
Veranstalter warnt - Betrug bei Festivals: So erkennen Fans gefälschte Tickets für Taubertal und Summer Breeze Taubertal-Festival und Summer Breeze 2027 sind bereits ausverkauft. Veranstalter und Verbraucherschützer warnen vor Betrugsmasche
What “dinkelsbuhl” means
WikipediaDinkelsbühl is a historic town in Central Franconia, a region of Germany that is now part of the state of Bavaria, in southern Germany. Dinkelsbühl is a former free imperial city of the Holy Roman Empire. In local government terms, Dinkelsbühl lies near the western edge of the Landkreis of Ansbach, north of Aalen.
“Dinkelsbühl” on Wikipedia (CC BY-SA) →#dinkelsbuhl across platforms
every network with a public tag surfaceFollow #dinkelsbuhl 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/dinkelsbuhl