#muenchensociallebt
Live, measured metrics for the hashtag #muenchensociallebt from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #muenchensociallebt
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-08-07 08:47 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-08-07 08:47 UTCNo related tags with measured usage found for #muenchensociallebt.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-08-07 08:47 UTCEverything below is measured over the latest 27 public posts (spanning ~8945 hours).
Posting hours (UTC) — busiest: 06:00
Languages: German (27)
Avg boosts / post: 44
Top of the latest posts
Troet.Cafe & Muenchen.Social Leben - ein Update #TroetCafeLebt Heute wurden die ersten Schritte zur „Rettung“ der Instanz besprochen und ein Team gegründet: Das Team Troet.Cafe. Martin wird weiterhin Admin und Leiter seiner Instanzen bleibe
Troet.Cafe und Muenchen.Social — 008.6 Okay, wow. Wir haben es geschafft. Ich würde Lügen wenn Ich sage das Ich alles verstehe was unsere nun große Gruppe an Helfenden herausgefunden hat, doch die Datenbank ist hergestellt, das Troet.Cafe a
Troet.Cafe & Muenchen.Social — 002 [Lest auch Martin's Ankündigung] Die Logs des in der Vergangenheit gescheiterten Update von muenchen.social sowie dem fehlerhaften postgresql Import von troet.cafe sind uns seit Montag (22.01.2024) zugängl
#muenchensociallebt across platforms
every network with a public tag surfaceFollow #muenchensociallebt 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/muenchensociallebt