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

Ford Galaxy 1.6 EcoBoost 160

The Ford Galaxy 1.6 EcoBoost 160 reaches 60 mph in 8.51 s (100 km/h in 9.52 s) and covers a standing quarter mile in 16.65 s, tripping the lights at 83.1 mph. It clears the first 60 ft in 2.55 s and the eighth mile in 10.75 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 1.6 EcoBoost 160 Renault Scenic 2.0 dCi 150

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 1.6 EcoBoost 160
0–60 mph8.51 s
0–100 km/h9.52 s
0–100 mph—
60 ft2.55 s
1/8 mile10.75 s
1/4 mile16.65 s
Trap speed83.1 mph

About the Galaxy 1.6 EcoBoost 160

The 2006 Ford Galaxy 1.6 EcoBoost 160 is a front-drive turbocharged MPV of 1,734 kg with 158 bhp, which works out at 91 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.55 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 7,520th quickest to 60 mph, and the 258th quickest of the 789 Fords here. Its 83.1 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 1.6 EcoBoost 160
Year2006
Power158 hp (118 kW)
Kerb mass1,734 kg
Power to weight91 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed125 mph (201 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Scenic 2.0 dCi 15020098.53 s16.63 s82.9 mph148 bhp
Citroen C8 2.2 HDi 17020028.60 s16.72 s82.7 mph168 bhp
Renault Grand Espace 3.0 dCi V6 24V 18020068.68 s16.65 s83.5 mph178 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 10 seconds10,136 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 1.6 EcoBoost 160 0-60 time?
The Ford Galaxy 1.6 EcoBoost 160 reaches 60 mph in 8.51 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,520th quickest of the 14,946 cars in the set.
What is the Ford Galaxy 1.6 EcoBoost 160 quarter mile time?
16.65 s at 83.1 mph. It reaches the eighth mile in 10.75 s and clears the first 60 ft in 2.55 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ford Galaxy 1.6 EcoBoost 160 have?
158 bhp and 1,734 kg, which is 91 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 201 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ford Galaxy 1.6 EcoBoost 160?
Closest here on pace: Renault Scenic 2.0 dCi 150 (8.53 s), Citroen C8 2.2 HDi 170 (8.60 s), Renault Grand Espace 3.0 dCi V6 24V 180 (8.68 s). Each one can be raced against the Ford Galaxy 1.6 EcoBoost 160 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 1.6 EcoBoost 160 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.