#criticalmasskaiserslautern
Live, measured metrics for the hashtag #criticalmasskaiserslautern from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #criticalmasskaiserslautern
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 15: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-08-07 15:51 UTCNo related tags with measured usage found for #criticalmasskaiserslautern.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-07 15:51 UTCEverything below is measured over the latest 4 public posts (spanning ~12441 hours).
Posting hours (UTC)
Languages: German (4)
Avg boosts / post: 2.8
Top of the latest posts
In #Kaiserslautern findet am kommenden Freitag 27.3. um 18 Uhr das Treffen zur #CriticalMass statt. Diesmal starten wir mit unseren Rädern in der 👉 #Stadtmitte zwischen #Fruchthalle und #Fackelbrunnen! Da wir mit mehr als 16 Teilnehmenden
In zwei Tagen (Fr 23.5. 18:00) haben wir in #Kaiserslautern wieder #CriticalMass. Aus dem aktuellen traurigen Anlass -es wurden vor ein paar Tagen #Stolpersteine der jüdischen Familie Herné in der Steinstraße ausgebrochen und gestohlen- wir
@CriticalMass „…Auch in #Kaiserslautern kam es zu dieser Antwort: Etwa 30 Teilnehmer einer "#CriticalMass"-Aktion machten den Ort der verschwundenen als auch der übrigen #Stolpersteine der Stadt zu Etappenzielen, erfuhren in kleinen Vorträg
#criticalmasskaiserslautern across platforms
every network with a public tag surfaceFollow #criticalmasskaiserslautern 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/criticalmasskaiserslautern