I posted a comment on this Seattle Bike Blog post with a basic cost analysis of the King County Bike Share Business Plan (site, PDF). This is the text of my comment.

At scale, the project forecasts 2200 bikes supported by an annual operating (not build out) cost of $4.6 million. That’s $2090/bike. It forecasts 2.68 million trips per year at an average of 2 miles/trip. If those numbers are accurate, a trip would cost $1.72. A mile, $0.86.

I don’t have a strong reaction to those costs. I would gladly pay $2/trip myself as an entirely usage-based fee. The forecasted cost is in line with Metro and Sound Transit fares. While it’s lower than their costs per boarding (for Metro, $3.70 in 2008; source), the shorter, denser routes are much cheaper to deliver than the system-wide average.

The data to compare route-level stats doesn’t exist. Shorter, denser routes are the closest comparables to phase 1. However, one could see bike sharing allowing the last mile of trips that would have otherwise been taken by car (and instead use bus or train). Not enough data to know.

My own conclusion: the costs are definitely “in the zone” for transit and might be a little cheaper than existing options.

Crucially, the total cost is incredibly small compared to any other transit implementation, and thereby, much lower risk. As a point of reference, Metro received $37.5 million to add 2 RapidRide Bus Rapid Transit (BRT) routes (source). Even excluding all other revenue sources, the total build out costs of all phases are equivalent to one BRT route.

As another perspective, the 4.3 mile Northgate light rail extension has a lifetime budget of $2.1 billion (70x-100x more than the total 5 year projected cost), and the South Lake Union Streetcar was $56.4 million (source).

I don’t mean to provide these as comparables. For me, the lower cost just means the barrier for my endorsement is much lower. In urban transit, $20 million is an experiment. In this case, the “experiment” happens to fund the whole system.


Source: King County Bike Share Business Plan (2012-01-27), pages 26-27, 36.