#BalticSynchronisation
Live, measured metrics for the hashtag #BalticSynchronisation from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #balticsynchronisation
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-01 07:37 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-01 07:37 UTCNo related tags with measured usage found for #balticsynchronisation.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-01 07:37 UTCEverything below is measured over the latest 11 public posts (spanning ~14783 hours).
Posting hours (UTC)
Languages: English (11)
Avg boosts / post: 0.2
Top of the latest posts
We are in Estonia 🇪🇪 visiting the construction works of some parts of the #BalticSynchronisation Project, a #PCI supported by #CEFEnergy with EUR 1,3 billion ⚡️ #EU #REPowerEU #ConnectingEurope 🐦🔗: https://n.respublicae.eu/cinea_eu/stat
Today Estonia, Latvia & Lithuania fully disconnect from Russian and Belarussian electricity grids and join the Continental Europe Network via Poland. They are now fully integrated into the EU internal energy market. 🔗 https://europa.eu/!hy
#BalticSynchronisation ⚡️#EnergyInfrastructure Europe by Satellite sends LIVE with Commissioner @DanJoergensen and Commissioner @KubiliusA from Vilnius, Lithuania🇱🇹 at 14.30 (CET). 📹 https://europa.eu/!Tx43kH --- https://nitter.privacyde
#balticsynchronisation across platforms
every network with a public tag surfaceFollow #balticsynchronisation 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/balticsynchronisation