#muenchendigitalerleben
Live, measured metrics for the hashtag #muenchendigitalerleben from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #muenchendigitalerleben
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-08-07 16:58 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-08-07 16:58 UTCNo related tags with measured usage found for #muenchendigitalerleben.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-07 16:58 UTCEverything below is measured over the latest 7 public posts (spanning ~12334 hours).
Posting hours (UTC)
Languages: German (7)
Avg boosts / post: 1.1
Top of the latest posts
„München 2030 - Digital sozial verantwortlich?!" Das war der Titel des Mediensalons, den wir im Rahmen unseres Netzwerks "Interaktiv" gemeinsam mit dem IT-Referat der LH München, Referentin Laura Dornheim @schwarzblond und dem Digitalrat re
Blinde Begeisterung? Wie das KVR beim Forum München Digital für Digitalisierung wirbt #fmd24 #MuenchenDigitalErleben
Selbst Mitarbeiter des IT-Referats sprechen von „kryptisch benannten Räumen“ im eigenen Haus. Das Leitsystem im IT-Rathaus ist stark verbesserungswürdig oder nur für Nerds begreifbar. Jetzt Vortrag über das KVR als digitales Amt im Raum P0.
#muenchendigitalerleben across platforms
every network with a public tag surfaceFollow #muenchendigitalerleben 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/muenchendigitalerleben