← My Auto Racer All cars Ford 0-60 Comparisons Answers

Ford Galaxy 2.0 EcoBoost 203

The Ford Galaxy 2.0 EcoBoost 203 reaches 60 mph in 7.93 s (100 km/h in 8.42 s) and covers a standing quarter mile in 16.18 s, tripping the lights at 86.5 mph. It clears the first 60 ft in 2.56 s and the eighth mile in 10.46 s.

Simulated, not measured — computed from published kerb mass, rated power, gearing and drivetrain, then fitted to this car’s own published acceleration figures. Dry asphalt, 20 °C, sea level, 1 ft rollout.

Ford Galaxy 2.0 EcoBoost 203 Toyota Verso 2.2 D-4D 177

Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.

Down the strip

Standing start Ford Galaxy 2.0 EcoBoost 203
0–60 mph7.93 s
0–100 km/h8.42 s
0–100 mph—
60 ft2.56 s
1/8 mile10.46 s
1/4 mile16.18 s
Trap speed86.5 mph

About the Galaxy 2.0 EcoBoost 203

The 2006 Ford Galaxy 2.0 EcoBoost 203 is a front-drive turbocharged MPV of 1,727 kg with 200 bhp, which works out at 116 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.56 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 6,370th quickest to 60 mph, and the 180th quickest of the 789 Fords here. Its 86.5 mph trap speed sits about where its 0-60 puts it, so it launches and pulls in roughly equal measure. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Ford Galaxy 2.0 EcoBoost 203
Year2006
Power200 hp (149 kW)
Kerb mass1,727 kg
Power to weight116 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed135 mph (217 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Toyota Verso 2.2 D-4D 17720097.87 s16.17 s86.5 mph174 bhp
Citroen Grand C4 Picasso 1.6 THP 16520167.83 s16.13 s86.0 mph162 bhp
Ford S-Max 2.0 TDCI 21020157.93 s16.18 s86.5 mph207 bhp

Picked for a fair race, not just a matching 0-60: pace, power-to-weight and body shape all count, and at most one is from the same maker.

Where these times sit

0-60 under 8 seconds6,514 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Ford 0-60 timesevery modelFastest MPVs and people carriers478 carsFastest cars of the 2000s5,138 cars
Put this race on your own page

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the Ford Galaxy 2.0 EcoBoost 203 0-60 time?
The Ford Galaxy 2.0 EcoBoost 203 reaches 60 mph in 7.93 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,370th quickest of the 14,946 cars in the set.
What is the Ford Galaxy 2.0 EcoBoost 203 quarter mile time?
16.18 s at 86.5 mph. It reaches the eighth mile in 10.46 s and clears the first 60 ft in 2.56 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ford Galaxy 2.0 EcoBoost 203 have?
200 bhp and 1,727 kg, which is 116 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 217 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ford Galaxy 2.0 EcoBoost 203?
Closest here on pace: Toyota Verso 2.2 D-4D 177 (7.87 s), Citroen Grand C4 Picasso 1.6 THP 165 (7.83 s), Ford S-Max 2.0 TDCI 210 (7.93 s). Each one can be raced against the Ford Galaxy 2.0 EcoBoost 203 in the panel at the top of this page. These are theoretical times from a physics simulation, not measured runs.
Are these real measured times?
No. Every figure on this page is produced by a physics simulation, not by a stopwatch at a drag strip. The Ford Galaxy 2.0 EcoBoost 203 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 published acceleration figures. Conditions are the same for every car in the set: dry asphalt, 20 °C, sea level, 1 ft rollout.

Figures regenerated 2026-10-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.