#Streckenplanung
Live, measured metrics for the hashtag #Streckenplanung from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #streckenplanung
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 · mas.to (Mastodon public tags API) · fetched 2026-10-24 10:57 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-10-24 10:57 UTCNo related tags with measured usage found for #streckenplanung.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-24 10:57 UTCEverything below is measured over the latest 5 public posts (spanning ~35026 hours).
Posting hours (UTC)
Languages: German (4) · English (1)
Avg boosts / post: 0.8
Top of the latest posts
Bahn-Milliardenprojekt: Bundestag gibt für Streckenplanung Augsburg-Ulm grünes Licht Der Bundestag hat grünes Licht für die weitere Planung zum Aus- und Neubau der ICE-Strecke zwischen Augsburg und… #Augsburg #Deutschland #Deutsch #DE #Schl
Für alle, die das geniale Tool #bikerouter von Marcus Jaschen zur Streckenplanung lieben: Es gibt eine tolle Neuigkeit, den Route Manager (Shift+e). Und was ich extrem super finde: Bookmarken im Webbrowser ohne Konto https://bikerouter.de M
#Berlin #Magnetschwebehahn #Streckenplanung #CDU #Vorschlag #MassiveKritikandererParteien Magnetschwebebahn für Berlin - Auf diesen Strecken könnte sie fahren: https://www.berliner-zeitung.de/mensch-metropole/magnetschwebebahn-fuer-berlin-a
#streckenplanung across platforms
every network with a public tag surfaceFollow #streckenplanung 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/streckenplanung