#UCTE
Live, measured metrics for the hashtag #UCTE from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ucte
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.online (Mastodon public tags API) · fetched 2026-11-10 00:32 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.online (Mastodon public search API) · fetched 2026-11-10 00:32 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-10 00:32 UTCEverything below is measured over the latest 29 public posts (spanning ~27832 hours).
Posting hours (UTC) — busiest: 11:00
Languages: German (27) · English (2)
Avg boosts / post: 0.6
Top of the latest posts
Netzfrequenzinfodienst *Auswertung* #Netzfrequenztrigger #RGCE #UCTE UTC : 03.04.2025 09:04:26 MESZ: 03.04.2025 11:04:26 Unterfrequenz :49,8890Hz Netzlastdifferenz : -1549 MW
RJ2-Netzfrequenzinfodienst -1-@RJ2Netzfrequenzinfodienst@nrw.social♥ 0↻ 02025-04-03 13:30 UTCView post →Netzfrequenzinfodienst *Auswertung* #Netzfrequenztrigger #RGCE #UCTE UTC : 03.04.2025 08:05:12 MESZ: 03.04.2025 10:05:12 Unterfrequenz :49,9000Hz Netzlastdifferenz : -1380 MW
RJ2-Netzfrequenzinfodienst -1-@RJ2Netzfrequenzinfodienst@nrw.social♥ 0↻ 02025-04-03 13:29 UTCView post →Netzfrequenzinfodienst *Auswertung* #Netzfrequenztrigger #RGCE #UCTE UTC : 03.04.2025 07:01:22 MESZ: 03.04.2025 09:01:22 Unterfrequenz :49,8150Hz Netzlastdifferenz : -2683 MW
RJ2-Netzfrequenzinfodienst -1-@RJ2Netzfrequenzinfodienst@nrw.social♥ 0↻ 02025-04-03 13:27 UTCView post →
#ucte across platforms
every network with a public tag surfaceFollow #ucte 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/ucte