#planfeststellungsverfahren
Live, measured metrics for the hashtag #planfeststellungsverfahren from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #planfeststellungsverfahren
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-08-08 20:38 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-08-08 20:38 UTCNo related tags with measured usage found for #planfeststellungsverfahren.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-08 20:38 UTCEverything below is measured over the latest 18 public posts (spanning ~29960 hours).
Posting hours (UTC) — busiest: 13:00
Languages: German (18)
Avg boosts / post: 0.4
Top of the latest posts
‼️Die #Inselgrünen rufen zu Stellungnahmen im "#Planfeststellungsverfahren #BaLWin5 /+525-kv-DC-Leitung, #Konverterplattform BaLWin epsilon - #Werderland Abschnitt Seetrasse - BaLWin 5 (NOR-9-4)" bis spätestens 15.5.2026 auf‼️ Die #TenneT O
#Europa #Deutschland #NRW #Ostwestfalen #Harsewinkel #Planfeststellungsverfahren #Verl #TWEStrecken #TWE9163 #TWE9164 Planfeststellungsverfahren für die Reaktivierung des Schienenpersonennahverkehrs auf den TWE-Strecken 9163 und 9164 (Harse
Was spricht für den Ausbau der Pendlerstraßen B51 und B64 - was dagegen? Darüber diskutieren Gegner und Befürworter in Telgte.#Stadtgespräch #Beelen #Warendorf #Herzebrock-Clarholz #Münster #Telgte #Westfalen #StudioMünster #B51 #B64 #B64n
#planfeststellungsverfahren across platforms
every network with a public tag surfaceFollow #planfeststellungsverfahren 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/planfeststellungsverfahren