Yes — it comes from the CityBikes API and is refreshed on a schedule.

No. This source is fully key-less.

Yes — free, no download, in your browser.

The General Bikeshare Feed Specification, a standardized data feed for the availability of shared mobility systems, created in 2014 and now governed by MobilityData. Apps use it to read station and bike availability in a consistent format.

Does this show how many bikes are available?

No. It lists the networks themselves. Bike and empty-slot counts live in each network’s own detail view, which this saver does not draw.

Bike Share Networks Screensaver

The Bike Share Networks screensaver shows every public bike-share system CityBikes tracks worldwide, read key-less from its own API. The site's Bike Share saver watches docks in one city; this is the global directory of who runs what, and where. It's free, runs in your browser, and ESC exits.

How the Bike Share Networks screensaver works

The saver reads the CityBikes API directly in your browser — no key and no account.

Every public bike-share system CityBikes tracks worldwide, read key-less from its own API.

It refreshes on a schedule, so what you see stays current.

Colours can be changed in settings; nothing is stored beyond your own browser.

CityBikes and the standard behind bike-share data

CityBikes publishes a directory of bike-share networks through its API. Each entry in the networks list has an id, a name, a company (the operator that runs it), and a location block with city, country, latitude and longitude. The project’s Python library, pybikes, collects the data from different websites and APIs behind one consistent interface, and the CityBikes project is built on it.

Many systems publish their own data in the General Bikeshare Feed Specification, or GBFS. It was created in 2014 by Mitch Vars with input from shared-mobility operators, app developers and vendors. The North American Bikeshare Association (NABSA) endorsed and hosted it from 2015, and in 2019 chose MobilityData to govern it. It describes the availability of shared mobility systems for rider-facing apps. In the CityBikes API, an individual network’s detail view can point to its GBFS feed through a gbfs_href field.

This saver reads the network directory, not the dock counts. The detailed view of a single network is where stations with bike and empty-slot counts appear. The list tells you who runs bike-share and where, and because each entry names a company, one operator can appear against several cities.

A worked example

Every public bike-share system CityBikes tracks worldwide, read key-less from its own API. The site's Bike Share saver watches docks in one city; this is the global directory of who runs what, and where.

Settings & tips

Accent and Background recolour the display.
Data comes straight from the CityBikes API in your browser.
Press ESC to leave fullscreen.

Frequently asked questions

Is this real data?: Yes — it comes from the CityBikes API and is refreshed on a schedule.
Is a key needed?: No. This source is fully key-less.
Is it free?: Yes — free, no download, in your browser.
What is GBFS?: The General Bikeshare Feed Specification, a standardized data feed for the availability of shared mobility systems, created in 2014 and now governed by MobilityData. Apps use it to read station and bike availability in a consistent format.
Does this show how many bikes are available?: No. It lists the networks themselves. Bike and empty-slot counts live in each network’s own detail view, which this saver does not draw.

← All World Live screensavers