#netzfrequenzsprung
Live, measured metrics for the hashtag #netzfrequenzsprung from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #netzfrequenzsprung
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-11-03 13:23 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-11-03 13:23 UTCNo related tags with measured usage found for #netzfrequenzsprung.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-11-03 13:23 UTCEverything below is measured over the latest 4 public posts (spanning ~15697 hours).
Posting hours (UTC)
Languages: German (4)
Avg boosts / post: 6.3
Used together with
Top of the latest posts
⚡ Heute Abend (23.10.2026) lohnt sich ein Blick auf die Netzfrequenz! Zum Stundenwechsel um 22:00 MESZ wird ein deutlicher Frequenzsprung erwartet. 📈 Kurz vor 22:00 Uhr reinschauen – es könnte spannend werden! https://www.rj2et.de/netzfreq
Netzfrequenzsprung Level 4, ∆f↓ = -165mHz in 30s ==> Netzlastdifferenz ≈ -2700MW https://rj2et.de/netzfrequenzsprung #Netzfrequenzinfodienst #Netzfrequenzsprung #RJ2ET
erste Analyse : Meldung 22:00 : Netzfrequenzsprung Level 4, ∆f↓ = -165mHz in 30s ==> Netzlastdifferenz ≈ -2700MW https://rj2et.de/netzfrequenzsprung #Netzfrequenzinfodienst #Netzfrequenzsprung #RJ2ET
#netzfrequenzsprung across platforms
every network with a public tag surfaceFollow #netzfrequenzsprung 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/netzfrequenzsprung