#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.

hashtag.org network · sponsored

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.

$5.00/ year · 18-character #name
Claim #netzfrequenzsprung$5.00/yrBuy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
1
Recent posts
Mastodon
Recent pace
Mastodon · last 1
0
Avg reactions / post
Mastodon · last 1
Reddit posts / month
Reddit search
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-08-02 16:38 UTC
0
07-27
0
07-28
0
07-29
0
07-30
0
07-31
0
08-01
0
08-02

0 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-02 16:38 UTC

No related tags with measured usage found for #netzfrequenzsprung.

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-02 16:38 UTC

Everything below is measured over the latest 1 public posts.

Posting hours (UTC)

00:0012:0023:00

Languages: German (1)

Avg boosts / post: 2

Used together with

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

    RJ2-Netzfrequenzinfodienst@[email protected]022025-01-07 19:32 UTCView post →

#netzfrequenzsprung across platforms

every network with a public tag surface

Follow #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