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

Opel Calibra 2.0 16V 150

The Opel Calibra 2.0 16V 150 reaches 60 mph in 8.21 s (100 km/h in 9.14 s) and covers a standing quarter mile in 16.55 s, tripping the lights at 86.4 mph. It clears the first 60 ft in 2.86 s and the eighth mile in 10.86 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 Calibra 2.0 16V 150 Volvo V70 2.4 170 (2004)

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 Calibra 2.0 16V 150
0–60 mph8.21 s
0–100 km/h9.14 s
0–100 mph—
60 ft2.86 s
1/8 mile10.86 s
1/4 mile16.55 s
Trap speed86.4 mph

About the Calibra 2.0 16V 150

The 1986 Opel Calibra 2.0 16V 150 is an all-wheel-drive naturally aspirated saloon of 1,300 kg with 148 bhp, which works out at 113 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.86 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 6,936th quickest to 60 mph, and the 146th quickest of the 721 Opels here. Its 86.4 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 Calibra 2.0 16V 150
Year1986
Power148 hp (110 kW)
Kerb mass1,300 kg
Power to weight113 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineNaturally aspirated
Top speed134 mph (216 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Volvo V70 2.4 170 (2004)20048.21 s16.52 s86.9 mph168 bhp
Nissan Altima 2.4 16V 15419988.19 s16.56 s86.4 mph152 bhp
Peugeot 407 2.2 16V 16320048.21 s16.52 s86.9 mph161 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 4x4s and all-wheel-drive cars2,981 carsFastest cars of the 1980s1,057 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 Calibra 2.0 16V 150 0-60 time?
The Opel Calibra 2.0 16V 150 reaches 60 mph in 8.21 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,936th quickest of the 14,946 cars in the set.
What is the Opel Calibra 2.0 16V 150 quarter mile time?
16.55 s at 86.4 mph. It reaches the eighth mile in 10.86 s and clears the first 60 ft in 2.86 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Opel Calibra 2.0 16V 150 have?
148 bhp and 1,300 kg, which is 113 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 5 gears and a quoted top speed of 216 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Opel Calibra 2.0 16V 150?
Closest here on pace: Volvo V70 2.4 170 (2004) (8.21 s), Nissan Altima 2.4 16V 154 (8.19 s), Peugeot 407 2.2 16V 163 (8.21 s). Each one can be raced against the Opel Calibra 2.0 16V 150 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 Calibra 2.0 16V 150 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.