#brandursachenermittlung
Live, measured metrics for the hashtag #brandursachenermittlung from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #brandursachenermittlung
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-27 04:19 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-27 04:19 UTCNo related tags with measured usage found for #brandursachenermittlung.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-27 04:19 UTCEverything below is measured over the latest 5 public posts (spanning ~4941 hours).
Posting hours (UTC)
Languages: German (5)
Avg boosts / post: 1
Top of the latest posts
Dahlem (ots) - Durch bislang unbekannte Personen wurde im Zeitraum von Sonntag (13. September) bis Sonntag (27. September), ein Brandschaden an der Schutzhütte "Finsterey" in Dahlem verursacht. Die Schutzhütte befindet sich in der Verlänger
Bad Münstereifel (ots) - Am gestrigen Dienstag, 15. September, kam es gegen 8.45 Uhr auf dem Sittardweg zu einem Brand in einem Müllwagen. Der Fahrer nahm während der Fahrt aufsteigenden Rauch aus dem Ladebereich sowie Brandgeruch wahr. Dar
Brand in Umkleidekabine (ots) - Am Mittwochmorgen (6. Mai) gegen 9.30 Uhr kam es in der Sporthalle einer Berufsschule an der Kommerner Straße in Euskirchen zu einem Brand in einer Umkleidekabine. Nach bisherigen Erkenntnissen wurde ein ...
#brandursachenermittlung across platforms
every network with a public tag surfaceFollow #brandursachenermittlung 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/brandursachenermittlung