Bike vs Tube in Traffic: Who Wins the Commute? - Terra Research

Bike vs Tube in Traffic: Who Wins the Commute? - Terra Research

Key point: on 1,628 fully matched trips, the bike beats TfL on 92% of journeys (median save 15 minutes) and beats Google rush-hour driving on 75% (median save 5 minutes).

Is cycling actually faster than the Tube for a London morning commute, or just more virtuous? Personally, I love commuting by bike, and I am not afraid to admit I’m a big fan of E-Bikes. I’d choose to use a bike even if it was slightly slower, to get some fresh air, see the sights, and move a little.

For this analysis, I matched 2,168 weekday wearable bike trips starting between 7–9 am against TfL journey times and Google traffic-aware driving for the same origin–destination pairs. The aim? To determine the within-trip deltas, or how many minutes the recorded bike ride wins or loses versus each counterfactual.

Where the Bike Wins

Figure 1: Trip-level time difference for the same morning origin–destination: bike duration minus the modeled alternative. Negative minutes mean the recorded bike ride was faster; green shading marks bike wins.

Most trips sit clearly left of zero versus public transport. Versus traffic, the distribution is tighter and closer to zero but still mostly green. There are more near-ties and losses on short hops where the car is competitive.

Get the latest Terra Research reports and insights every week as soon as they're published.

By continuing, I agree to the Privacy Policy and Terms of Service.

Wins by Journey Length

I split matched trips into short (<6 km), medium (6–15 km), and long (15–25 km) bands. Win rates and median savings both stay with the bike, but the opponent changes with distance. I’m surprised by these results, as I suspected the bike's advantage to be removed over the longer distances.

But this dataset is probably populated by quite serious commuters who aren’t opposed to commuting long distances. We also can’t discount the possibility that more people commute longer distances when there are travel problems with the other options, eg tube strikes.

08_win_rates_by_length (1).svg — Figure 2: Share of matched morning trips where the recorded bike ride beats TfL door-to-door or Google traffic driving. Short <6 km, medium 6–15 km, long 15–25 km, win rates stay high across lengths, with traffic wins peaking mid-distance.

Figure 3: Median minutes saved on the same origin–destination when cycling versus TfL or Google rush-hour driving. This is a within-trip delta, not a comparison of different absolute journey lengths across modes.

Short rides have a big win over the Tube but only narrowly beat (or sometimes lose to) a car in traffic. Medium rides are the sweet spot: still ~94% wins versus TfL, and traffic wins jump to 84% with about 9 minutes saved. For longer commutes, the Tube becomes a more competitive option, while the bike’s median save versus rush-hour driving stays large.

Wins on Busy Corridors

The ten most frequent multi-user corridors are mostly radial rides into the City, Canary Wharf, and central London. On these routes, cycling typically saves about 15 minutes versus TfL and about 8 minutes versus Google rush-hour driving.

Figure 4: Busiest multi-user morning bike corridors over a Greater London silhouette with the Thames. Blue routes beat Google rush-hour driving; orange means traffic still wins.

Figure 5: Each corridor has two bars: minutes saved versus public transport and versus Google rush-hour driving. Positive values mean the bike is faster; Ilford → Barking is the main case where Google driving still wins on time.

Corridor	Bike	vs PT	vs Google drive
Shepherd's Bush → Kensington	13 min	−12 min	−1 min
Isle of Dogs → Canary Wharf	10 min	−12 min	−1 min
Lewisham → City	26 min	−14 min	−5 min
Hammersmith → City	31 min	−25 min	−18 min
Hackney → City	24 min	+1 min	−1 min
Wandsworth → City	31 min	−19 min	−26 min
Clapham → City	37 min	−15 min	−7 min
Isle of Dogs → City	24 min	−7 min	−15 min
Hackney → Central London	21 min	−23 min	−14 min
Ilford → Barking	47 min	−27 min	+11 min

Negative minutes mean the bike is faster. Hammersmith → City and Wandsworth → City are standouts against traffic. Hackney → City remains the rare Tube-competitive corridor. Ilford → Barking is the exception versus Google driving, longer outer-London trips are where the car still wins on time.

Methodology

I used a database of outdoor cycling activities on Weekdays in Greater London with local starts from 07:00–08:59, distances of 1–25 km, and durations of 5–90 minutes. That leaves a commute-like cohort.

For each trip I estimated counterfactual travel times:

Public transport: TfL Journey Planner API with door-to-door walking using the same hour/minute on the nearest matching weekday.
Driving (rush hour): Google Routes API for the next matching weekday at the same departure time.

Important caveat: I only see the recorded bike activity. Wearables don’t tell me whether that ride is the full door-to-door commute. Someone may walk to a bike share, cycle part of the way, then take the Tube, or start/stop the activity mid-journey, so the bike times can miss walking legs or other modes at either end.

I think this sample is predominantly “serious” cyclists, so most journeys are probably door-to-door. But I am guessing on that point. By contrast, the TfL and Google estimates are built as full origin–destination journeys. Treat the comparison as bike segment vs door-to-door alternatives, not a perfect like-for-like door-to-door race.

Takeaway

On matched morning origin–destinations, the bike wins most of the time, ~92% versus TfL and ~75% versus Google traffic. With the biggest traffic advantage on medium-length radial rides. Short trips still thrash the Tube/public transport but are closer versus the car; long trips keep solid win rates with larger median savings against traffic. Get on your bike!

Summary questions

Is cycling actually faster than the Tube for a London morning commute?: Yes, and it's not close. Across 1,628 matched morning trips, the bike beat TfL door-to-door times on roughly 92% of journeys, with a median saving of 15 minutes. Public transport was only competitive on a single corridor in the analysis — Hackney → City — where the Tube edged the bike by about a minute.
Does the bike also beat driving in rush-hour traffic?: Most of the time, yes. The bike beat Google's traffic-aware driving estimate on about 75% of matched trips, with a median saving of 5 minutes. The car only reliably wins on longer outer-London routes like Ilford → Barking, where driving was about 11 minutes faster.
What commute distance gives cycling the biggest edge?: Medium-distance rides of 6–15 km are the sweet spot. In that band, the bike wins ~94% of matchups versus TfL and jumps to an 84% win rate against rush-hour driving, saving around 9 minutes versus the car. Short trips under 6 km crush the Tube but are much closer to a coin flip versus driving.
Do longer bike commutes lose their advantage?: Surprisingly, no. On 15–25 km trips the bike still posts strong win rates and actually keeps a large median time saving against rush-hour driving. The Tube becomes more competitive at long distances, but the car struggles more with traffic over those spans — and the cohort here skews toward serious commuters willing to ride that far.
Which London corridors favor cycling the most?: Radial routes into the City are where the bike dominates. Hammersmith → City saves about 31 minutes versus public transport and 18 minutes versus driving; Wandsworth → City saves 31 minutes versus TfL and 26 minutes versus traffic; Clapham → City saves 37 minutes versus the Tube. The ten busiest corridors average roughly 15 minutes saved versus TfL and 8 minutes versus driving.
Are there any commutes where I should still drive or take the Tube?: A few. Ilford → Barking is the clearest driving win, with the car about 11 minutes faster — outer-London trips are where traffic-aware driving still beats the bike. Hackney → City is the one corridor where the Tube edges cycling, by about a minute. Otherwise, the bike is the faster mode.
How were the bike, Tube, and driving times actually compared?: The analysis matched 2,168 weekday wearable bike activities in Greater London starting 07:00–08:59, 1–25 km and 5–90 minutes long. For each trip, the TfL Journey Planner API produced a door-to-door public transport estimate and the Google Routes API produced a traffic-aware driving estimate for the same origin–destination and departure time, yielding within-trip deltas rather than cross-mode averages.
Can wearable bike data really capture a full door-to-door commute?: Not perfectly. Wearables only record the cycling segment, so any walking, bike-share pickup, or multi-modal legs at either end are invisible, while the TfL and Google counterfactuals are full door-to-door journeys. The cohort here looks like serious cyclists whose rides are likely near door-to-door, but the fair framing is bike segment vs full-journey alternatives — and even with that handicap, the bike still wins ~92% and ~75% of the time.