#zypresse
Live, measured metrics for the hashtag #zypresse from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #zypresse
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-28 12: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-28 12:58 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-28 12:58 UTCEverything below is measured over the latest 2 public posts (spanning ~2179 hours).
Posting hours (UTC)
Languages: German (2)
Avg boosts / post: 1.5
Top of the latest posts
Zypresse am Schloss Charlottenburg #ThickTrunkTuesday #Trees #Zypresse #Berlin
Kurioser Fall: 1 Gericht in #CostaRica entscheidet nach etwa 3 Jahren, dass #Zypresse|n, die im #Zentraltal in ca. 1850m Höhe wachsen, gefällt werden müssen. Sie würden das Grundstück einer Nachbarin gefährden. Es regt sich Widerstand in de
#zypresse across platforms
every network with a public tag surfaceFollow #zypresse 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/zypresse