#Bikeability
Live, measured metrics for the hashtag #Bikeability from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bikeability
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-07-29 16:07 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-07-29 16:07 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 16:07 UTCEverything below is measured over the latest 27 public posts (spanning ~31663 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (23) · German (3) · Swedish (1)
Avg boosts / post: 2.8
Top of the latest posts
Good news: we just released #NetAScore version 1.0 - #opensource tool for computing #bikeability and #walkability from #OSM data https://github.com/plus-mobilitylab/netascore #Mobility #NetworkAnalysis #GIS
Interested in #bikeability and #walkability assessment? Have you heard of NetAScore? Our new article in "Environment and Planning B" introduces the #opensource software NetAScore for segment-based bikeability and walkability using #OSM data
🚴♂️ 📝 🚴♀️ How suitable are roads for everyday #cycling? Please help us in our #research and participate in this short online #survey on #bikeability (+ spread the invitation): https://websurvey.zgis.at/index.php/173238?lang=en
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/bikeability