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

Vauxhall Meriva 1.7 CDTi 110 (2010)

The Vauxhall Meriva 1.7 CDTi 110 (2010) reaches 60 mph in 10.72 s (100 km/h in 11.37 s) and covers a standing quarter mile in 17.82 s, tripping the lights at 76.8 mph. It clears the first 60 ft in 2.66 s and the eighth mile in 11.43 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.

Vauxhall Meriva 1.7 CDTi 110 (2010) Lancia Voyager 2.8 163

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 Vauxhall Meriva 1.7 CDTi 110 (2010)
0–60 mph10.72 s
0–100 km/h11.37 s
0–100 mph—
60 ft2.66 s
1/8 mile11.43 s
1/4 mile17.82 s
Trap speed76.8 mph

About the Meriva 1.7 CDTi 110

The 2010 Vauxhall Meriva 1.7 CDTi 110 (2010) is a front-drive turbodiesel MPV of 1,360 kg with 109 bhp, which works out at 80 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.66 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 11,258th quickest to 60 mph, and the 108th quickest of the 164 Vauxhalls here. Its 76.8 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 Vauxhall Meriva 1.7 CDTi 110 (2010)
Year2010
Power109 hp (81 kW)
Kerb mass1,360 kg
Power to weight80 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed113 mph (182 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lancia Voyager 2.8 163201110.75 s17.85 s77.2 mph161 bhp
Chevrolet Orlando 1.8 141201010.65 s17.82 s76.6 mph138 bhp
Renault Scenic 1.2 TCe 115 (2013)201310.63 s17.75 s77.1 mph113 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Vauxhall 0-60 timesevery modelFastest MPVs and people carriers478 carsFastest cars of the 2010s4,541 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 Vauxhall Meriva 1.7 CDTi 110 (2010) 0-60 time?
The Vauxhall Meriva 1.7 CDTi 110 (2010) reaches 60 mph in 10.72 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,258th quickest of the 14,946 cars in the set.
What is the Vauxhall Meriva 1.7 CDTi 110 (2010) quarter mile time?
17.82 s at 76.8 mph. It reaches the eighth mile in 11.43 s and clears the first 60 ft in 2.66 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Vauxhall Meriva 1.7 CDTi 110 (2010) have?
109 bhp and 1,360 kg, which is 80 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 182 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Vauxhall Meriva 1.7 CDTi 110 (2010)?
Closest here on pace: Lancia Voyager 2.8 163 (10.75 s), Chevrolet Orlando 1.8 141 (10.65 s), Renault Scenic 1.2 TCe 115 (2013) (10.63 s). Each one can be raced against the Vauxhall Meriva 1.7 CDTi 110 (2010) 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 Vauxhall Meriva 1.7 CDTi 110 (2010) 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.