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

Vauxhall Meriva 1.6 CDTi 110

The Vauxhall Meriva 1.6 CDTi 110 reaches 60 mph in 11.36 s (100 km/h in 12.06 s) and covers a standing quarter mile in 18.14 s, tripping the lights at 75.2 mph. It clears the first 60 ft in 2.72 s and the eighth mile in 11.63 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.6 CDTi 110 Renault Grand Scenic 1.2 Tce 115

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.6 CDTi 110
0–60 mph11.36 s
0–100 km/h12.06 s
0–100 mph—
60 ft2.72 s
1/8 mile11.63 s
1/4 mile18.14 s
Trap speed75.2 mph

About the Meriva 1.6 CDTi 110

The 2014 Vauxhall Meriva 1.6 CDTi 110 is a front-drive turbodiesel MPV of 1,403 kg with 109 bhp, which works out at 77 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.72 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 12,091st quickest to 60 mph, and the 125th quickest of the 164 Vauxhalls here. Its 75.2 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.6 CDTi 110
Year2014
Power109 hp (81 kW)
Kerb mass1,403 kg
Power to weight77 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed115 mph (185 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Grand Scenic 1.2 Tce 115201611.37 s18.08 s76.9 mph114 bhp
Renault Espace 2.0 16V 140 (2006)200611.37 s18.24 s76.1 mph134 bhp
Citroen C4 Picasso 1.6 HDiF 110200711.32 s18.29 s75.2 mph107 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.6 CDTi 110 0-60 time?
The Vauxhall Meriva 1.6 CDTi 110 reaches 60 mph in 11.36 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 12,091st quickest of the 14,946 cars in the set.
What is the Vauxhall Meriva 1.6 CDTi 110 quarter mile time?
18.14 s at 75.2 mph. It reaches the eighth mile in 11.63 s and clears the first 60 ft in 2.72 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Vauxhall Meriva 1.6 CDTi 110 have?
109 bhp and 1,403 kg, which is 77 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 185 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Vauxhall Meriva 1.6 CDTi 110?
Closest here on pace: Renault Grand Scenic 1.2 Tce 115 (11.37 s), Renault Espace 2.0 16V 140 (2006) (11.37 s), Citroen C4 Picasso 1.6 HDiF 110 (11.32 s). Each one can be raced against the Vauxhall Meriva 1.6 CDTi 110 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.6 CDTi 110 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.