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

Opel Grandland X 1.6 224

The Opel Grandland X 1.6 224 reaches 60 mph in 8.05 s (100 km/h in 8.52 s) and covers a standing quarter mile in 16.20 s, tripping the lights at 86.9 mph. It clears the first 60 ft in 2.54 s and the eighth mile in 10.48 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.

Opel Grandland X 1.6 224 DS Automobiles DS 7 Crossback E-Tense 1.6 PureTech PHEV 225

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 Opel Grandland X 1.6 224
0–60 mph8.05 s
0–100 km/h8.52 s
0–100 mph—
60 ft2.54 s
1/8 mile10.48 s
1/4 mile16.20 s
Trap speed86.9 mph

About the Grandland X 1.6 224

The 2017 Opel Grandland X 1.6 224 is a front-drive turbocharged SUV of 1,800 kg with 177 bhp, which works out at 98 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.54 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,623rd quickest to 60 mph, and the 108th quickest of the 721 Opels here. Its 86.9 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 Opel Grandland X 1.6 224
Year2017
Power177 hp (132 kW)
Kerb mass1,800 kg
Power to weight98 bhp/t
DrivetrainFront drive
Gears8
EngineTurbocharged
Top speed140 mph (225 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
DS Automobiles DS 7 Crossback E-Tense 1.6 PureTech PHEV 22520178.05 s16.20 s86.9 mph177 bhp
Jeep Compass 1.3 4x2 15020198.07 s16.31 s84.6 mph148 bhp
Hyundai Tucson 1.6 T-GDI 17720188.08 s16.27 s82.8 mph174 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
Opel 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 Opel Grandland X 1.6 224 0-60 time?
The Opel Grandland X 1.6 224 reaches 60 mph in 8.05 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,623rd quickest of the 14,946 cars in the set.
What is the Opel Grandland X 1.6 224 quarter mile time?
16.20 s at 86.9 mph. It reaches the eighth mile in 10.48 s and clears the first 60 ft in 2.54 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Opel Grandland X 1.6 224 have?
177 bhp and 1,800 kg, which is 98 bhp per tonne. It is front-drive, turbocharged, with 8 gears and a quoted top speed of 225 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Opel Grandland X 1.6 224?
Closest here on pace: DS Automobiles DS 7 Crossback E-Tense 1.6 PureTech PHEV 225 (8.05 s), Jeep Compass 1.3 4x2 150 (8.07 s), Hyundai Tucson 1.6 T-GDI 177 (8.08 s). Each one can be raced against the Opel Grandland X 1.6 224 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 Opel Grandland X 1.6 224 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.