#routenplaner
Live, measured metrics for the hashtag #routenplaner from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #routenplaner
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-10 15:43 UTC1 uses by 1 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-10 15:43 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-10 15:43 UTCEverything below is measured over the latest 34 public posts (spanning ~51352 hours).
Posting hours (UTC) — busiest: 06:00
Languages: German (34)
Avg boosts / post: 1.8
Top of the latest posts
@warumichradfahre hast du mal versucht, was dir #bikerouter (https://bikerouter.de) mit dem einen oder anderen Profil für eine Strecke vorschlägt? Meine ersten Favoriten sind stets: - Rennrad (sehr wenig Verkehr) - Gravel "quaelnix" - Trekk
Mit dem Bikerouter lassen sich detaillierte Fahrradrouten planen. Entwickler Marcus Jaschen spricht über Funktionen und seine Motivation. #Bikerouter #MarcusJaschen #Podcast #Routenplaner #Antritt https://detektor.fm/digital/antritt-marcus-
Damit ist es jetzt tatsächlich soweit - die #Avespfade gehen offline. Insofern schade, als dass ich eine zuverlässige, schlichte und vor allem genAI-lose Alternative für wertvoll halte, aber irgendwo leider auch einfach konsequent. Damit ma
#routenplaner across platforms
every network with a public tag surfaceFollow #routenplaner 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/routenplaner