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

Vauxhall Mokka 1.7 CDTI 131

The Vauxhall Mokka 1.7 CDTI 131 reaches 60 mph in 10.37 s (100 km/h in 11.06 s) and covers a standing quarter mile in 17.68 s, tripping the lights at 77.2 mph. It clears the first 60 ft in 2.69 s and the eighth mile in 11.31 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 Mokka 1.7 CDTI 131 Hyundai Tucson 1.6 CRDi 136 (Mk3)

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 Mokka 1.7 CDTI 131
0–60 mph10.37 s
0–100 km/h11.06 s
0–100 mph—
60 ft2.69 s
1/8 mile11.31 s
1/4 mile17.68 s
Trap speed77.2 mph

About the Mokka 1.7 CDTI 131

The 2012 Vauxhall Mokka 1.7 CDTI 131 is a front-drive turbodiesel SUV of 1,504 kg with 129 bhp, which works out at 86 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.69 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 10,726th quickest to 60 mph, and the 98th quickest of the 164 Vauxhalls here. Its 77.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 Mokka 1.7 CDTI 131
Year2012
Power129 hp (96 kW)
Kerb mass1,504 kg
Power to weight86 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed114 mph (183 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Hyundai Tucson 1.6 CRDi 136 (Mk3)201810.36 s17.66 s77.9 mph134 bhp
Mitsubishi Pajero/Montero/Shogun SWB 3.2 DI-D 165200010.37 s17.77 s76.7 mph162 bhp
Lancia Musa 1.9 Multijet 110200310.41 s17.77 s77.3 mph109 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 SUVs2,049 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 Mokka 1.7 CDTI 131 0-60 time?
The Vauxhall Mokka 1.7 CDTI 131 reaches 60 mph in 10.37 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,726th quickest of the 14,946 cars in the set.
What is the Vauxhall Mokka 1.7 CDTI 131 quarter mile time?
17.68 s at 77.2 mph. It reaches the eighth mile in 11.31 s and clears the first 60 ft in 2.69 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Vauxhall Mokka 1.7 CDTI 131 have?
129 bhp and 1,504 kg, which is 86 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 183 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Vauxhall Mokka 1.7 CDTI 131?
Closest here on pace: Hyundai Tucson 1.6 CRDi 136 (Mk3) (10.36 s), Mitsubishi Pajero/Montero/Shogun SWB 3.2 DI-D 165 (10.37 s), Lancia Musa 1.9 Multijet 110 (10.41 s). Each one can be raced against the Vauxhall Mokka 1.7 CDTI 131 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 Mokka 1.7 CDTI 131 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.