#leutersberg
Live, measured metrics for the hashtag #leutersberg from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #leutersberg
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-09-29 06:04 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-09-29 06:04 UTCNo related tags with measured usage found for #leutersberg.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-09-29 06:04 UTCEverything below is measured over the latest 3 public posts (spanning ~8523 hours).
Posting hours (UTC)
Languages: German (3)
Avg boosts / post: 0.7
Top of the latest posts
@freiburg & @RPFreiburg, wenn mir auf der Strecke zwischen #freiburg #stgeorgen und #leutersberg bzw. #schallstadt regelmäßig mindestens so viele #fahrradfahrer wie #Autofahrer begegnen - wäre es dann nicht langsam mal an der Zeit, die Gefa
@freiburg @RPFreiburg 3/ Im übrigen hat der ganze #fahrradweg zwischen der Engstelle in #freiburg #leutersberg und #schallstadt keine angemessene Breite, zusätzlich zur gruseligen 360-Grad-Kurvenunterführung kurz vor Schallstadt.
Gestern #mdrza #mdrnh (1) gemeinsamer Zweirichtungs-Fuß- und #Fahrradweg in #basel #schweiz. Geschätzte 5 Meter (!) breit. (2) alter #Zweirichtungsradweg in #frankreich. Geschätzte 2 Meter breit. (3) Engstelle in #freiburg an der Straße nac
#leutersberg across platforms
every network with a public tag surfaceFollow #leutersberg 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/leutersberg