#kummersbruck
Live, measured metrics for the hashtag #kummersbruck from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #kummersbruck
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-10-19 16:51 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-10-19 16:51 UTCNo related tags with measured usage found for #kummersbruck.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-19 16:51 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: German (1)
Avg boosts / post: 0
Top of the latest posts
Mann wirft Betonplatte ins Gleis – und räumt sie anschließend weg https://bahnblogstelle.com/220277/mann-wirft-betonplatte-aufs-gleis-und-raeumt-sie-anschliessend-weg/ #Betonplatte #Gleis #Bahnstrecke #Kümmersbruck #AmbergSulzbach #Bayern #
What “kummersbruck” means
WikipediaKümmersbruck is a municipality in the Amberg-Sulzbach district, in the state of Bavaria, Germany. It is situated 3 km southeast of Amberg. A division of the German Military is stationed here. Kümmersbruck is split up in 7 districts: Kümmersbruck, Haselmühl, Gärmersdorf, Moos, Haidweiher, Penkhof, Lengenfeld and Engelsdorf. The river Vils crosses the municipality.
“Kümmersbruck” on Wikipedia (CC BY-SA) →#kummersbruck across platforms
every network with a public tag surfaceFollow #kummersbruck 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/kummersbruck