#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 · mastodon.social (Mastodon public tags API) · fetched 2026-10-16 13:33 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-10-16 13:33 UTCNo related tags with measured usage found for #netzfrequenzsprung.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-16 13:33 UTCEverything below is measured over the latest 3 public posts (spanning ~25774 hours).
Posting hours (UTC)
Languages: German (3)
Avg boosts / post: 1
Top of the latest posts
Netzfrequenzinfodienst Manuelle Nachsendung #Netzfrequenzsprung #RGCE #UCTE UTC : 06.01.2025 21:05:14 MEZ : 06.01.2025 22:05:14 mains frequency jump evaluation df/dt : -165mHz / 42s Mains load change : Δ -2653 MW
Netzfrequenzinfodienst *Auswertung* #Netzfrequenzsprung #RGCE #UCTE UTC : 01.01.2025 21:00:19 MEZ : 01.01.2025 22:00:19 mains frequency jump evaluation df/dt : -142mHz/71s Mains load change : Δ -2177 MW
Na? Wieder Netzachterbahn durch Börsenzockerei? >_> --- RT @_RG_CE #Netzfrequenzinfodienst #Netzfrequenz #mainsfrequency *Auswertung* #Netzfrequenzsprung RG-CE possible #grid_split #RG-CE (#UCTE) UTC : 29.01.2022 21:00:17 MEZ : 29.01.2022 2
#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