Travel Time Calculator

Travel Speed Guide

What do I need to know about Realistic Average Speeds?

Real-world average speeds include stops, traffic, and route inefficiency. Car on motorway (M25 excluded): 80–90 km/h average including service breaks. Urban driving: 25–35 km/h in cities, 40–55 km/h in towns and suburbs. Intercity trains (Avanti West Coast, LNER): 120–160 km/h average including station stops. Regional trains: 60–90 km/h average. Cycling: 20–25 km/h for a fit commuter, 16–20 km/h for leisure. Walking: 4–5 km/h. These are block-to-block averages — actual journey times depend heavily on traffic signals, junction density, and terrain, so treat them as a reasonable planning estimate rather than a precise prediction.

Why Trains Beat Cars on Long Distance?

On the UK's main intercity routes (London–Manchester, London–Edinburgh, London–Birmingham), trains are consistently faster than cars door-to-door for single travellers. London–Manchester: car 2.5–3.5 hours (traffic and parking dependent) vs Avanti train 2:06 (fastest). London–Edinburgh: car 6–8 hours vs LNER train 4:23 (fastest). The advantage narrows for car journeys with multiple people (door-to-door convenience) and for destinations not well-served by rail.

What's the key thing to understand about Cycling Speed Factors?

Cycling speed varies significantly with fitness, bike type, terrain, and weather. E-bike: 25–30 km/h average (UK speed limit for electric assist). Road bike / commuter: 20–25 km/h. Mountain bike on road: 18–22 km/h. Cycling is time-competitive with driving for urban journeys under 10km — no parking time, no congestion, and predictable timing. For a 5km urban commute, cycling (15 minutes) frequently beats driving (10–25 minutes including parking) door-to-door.

What's the key thing to understand about Flight Time Calculations?

Flight travel time should include realistic airport times: arrival at airport (minimum 1.5–2hr for short-haul, 2.5–3hr for long-haul), boarding and taxi (30–45 min), actual flight, landing and taxiing (30 min), baggage reclaim (15–45 min), and transfer to destination. A 1-hour flight London–Amsterdam is realistically 5–6 hours total (door-to-door Eurostar is faster at 3:41). A 7-hour transatlantic flight is approximately 12–13 hours total.

What's the key thing to understand about Buffer Time for Connections and Delays?

A travel time calculation based on scheduled or average speeds gives a best-case estimate, but real journeys involve variability that a straightforward distance-and-speed calculation doesn't capture — traffic incidents, roadworks, train delays, and connection timing at interchanges all add risk of running later than the raw calculation suggests. For driving, a reasonable approach is to add a buffer proportional to journey length and road type: a short local trip needs little buffer, while a long motorway journey through areas prone to congestion deserves a more generous margin. For multi-leg journeys involving a train or flight connection, the buffer needed depends heavily on how the connection is structured — a tight connection between two separately-booked trains carries real risk of a missed connection if the first train runs even a few minutes late, while a single through-ticket itinerary, or a connection with a long gap built in, is far more forgiving. For any time-critical journey (catching a flight, an important meeting), it's worth treating a travel time calculator's output as the minimum likely duration, not a guarantee, and building in buffer accordingly.

What should I know about How Time of Day Changes Driving Time Estimates?

Average driving speed assumptions baked into a simple distance-based calculation can be significantly optimistic or pessimistic depending on when you actually travel. The same route driven during morning or evening rush hour in or around a major urban area can take considerably longer than the identical route driven at a quieter time of day, purely due to congestion rather than distance or speed limits changing. Motorway journeys are generally less affected by time-of-day variation than routes through or near city centres, though they're not immune, particularly around major junctions or where roadworks are present. If a journey's timing is flexible, checking typical congestion patterns for the specific route and adjusting departure time — leaving earlier or later to avoid the worst of rush hour — can sometimes save more time than any other single change, including choosing a faster-looking route on a map that turns out to pass through heavily congested areas at the time you'd actually be travelling.

How Do You Accurately Add Up a Multi-Modal Journey?

Journeys combining several modes of transport — a train followed by a bus, or a flight followed by a taxi — require more careful time budgeting than a single-mode journey, because the connection points between modes introduce both planned transfer time and a real risk of delay cascading through the rest of the trip. The most common mistake is adding up only the scheduled travel time for each leg and ignoring realistic transfer time between them — walking from a platform to a bus stop, clearing an airport after landing, or simply finding the right connecting service in an unfamiliar station all take genuine time that a simple timetable addition misses. A reasonable approach is to build in a buffer specific to each type of connection: a same-station train-to-train connection might need only 10-15 minutes, while an airport arrival followed by onward ground transport often needs 45-60 minutes or more to allow for disembarking, baggage collection if checked luggage is involved, and clearing the terminal. Multi-modal journeys are also more vulnerable to a single delay affecting the whole trip, since a late first leg can mean missing a connection on a fixed-schedule second leg, with no guarantee the next available connection runs soon after — this risk is highest when connections are tight and the connecting service runs infrequently. For any multi-modal journey with a time-critical endpoint (a flight to catch, an event to attend), building in a more generous buffer at the connection most likely to run late, or least frequently serviced if missed, protects against the overall trip time estimate being wrong.

Typical Average Speeds by Mode of Transport

Average realistic speeds differ substantially from a vehicle's top speed because they account for traffic, stops, boarding and terrain.

These are planning averages, not constants — a single journey often blends several of these speeds (urban roads at each end of a motorway trip, for example), which is why multi-leg journey estimates should be built up leg by leg rather than applying one flat average speed to the whole distance.

Worked Example: Driving vs Train for a 150-Mile Trip

For a 150-mile (240km) journey, driving at a realistic average of 55mph (accounting for some urban roads and a motorway section) takes approximately 150 ÷ 55 ≈ 2 hours 45 minutes of driving time, plus any fuel or rest stops. The equivalent intercity train journey, averaging perhaps 75mph including stops, takes roughly 150 ÷ 75 = 2 hours of in-transit time — but door-to-door this needs adding time to reach the station, wait for departure, and travel from the arrival station to the final destination, which can add 30-60 minutes on each end. Depending on how central the stations are relative to the actual start and end points, driving and train can end up remarkably close in total door-to-door time even though the train is faster while actually moving.

How Time of Day Changes Driving Time Estimates

The same route can take substantially longer during peak traffic hours than during off-peak periods, particularly on urban and suburban stretches near major cities. A journey that averages 45mph in free-flowing traffic might drop to an effective average of 20-25mph during a weekday morning or evening rush hour on a congested urban approach road, even though the motorway sections of the same trip are largely unaffected. For trips with a flexible start time, shifting departure by even 30-60 minutes outside peak commuting windows can meaningfully reduce total journey time on routes that pass through or near city centres, which is why point-to-point driving time estimates are best treated as a baseline that should be adjusted upward for any portion of the route that overlaps with known rush-hour congestion.