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

Opel Omega Sedan 2.5i V6 170

The Opel Omega Sedan 2.5i V6 170 reaches 60 mph in 8.70 s (100 km/h in 9.14 s) and covers a standing quarter mile in 16.85 s, tripping the lights at 87.6 mph. It clears the first 60 ft in 2.96 s and the eighth mile in 11.12 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 Omega Sedan 2.5i V6 170 Holden Vectra Sedan 2.2 147

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 Omega Sedan 2.5i V6 170
0–60 mph8.70 s
0–100 km/h9.14 s
0–100 mph—
60 ft2.96 s
1/8 mile11.12 s
1/4 mile16.85 s
Trap speed87.6 mph

About the Omega Sedan 2.5i V6 170

The 1999 Opel Omega Sedan 2.5i V6 170 is a rear-drive naturally aspirated saloon of 1,600 kg with 168 bhp, which works out at 105 bhp per tonne. Rear drive and 105 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.96 s. Against the 14,946 cars in the set it is the 7,871st quickest to 60 mph, and the 198th quickest of the 721 Opels here. It traps higher than its 0-60 suggests — 87.6 mph, the 6,084th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Opel Omega Sedan 2.5i V6 170
Year1999
Power168 hp (125 kW)
Kerb mass1,600 kg
Power to weight105 bhp/t
DrivetrainRear drive
Gears5
EngineNaturally aspirated
Top speed142 mph (228 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Holden Vectra Sedan 2.2 14719958.67 s16.88 s85.7 mph145 bhp
Volvo S80 2.0 D4 16320098.70 s16.72 s82.9 mph161 bhp
Renault Vel Satis 2.0 16V Turbo 17020058.67 s16.70 s83.8 mph168 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 saloon cars3,808 carsFastest cars of the 1990s2,649 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 Omega Sedan 2.5i V6 170 0-60 time?
The Opel Omega Sedan 2.5i V6 170 reaches 60 mph in 8.70 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,871st quickest of the 14,946 cars in the set.
What is the Opel Omega Sedan 2.5i V6 170 quarter mile time?
16.85 s at 87.6 mph. It reaches the eighth mile in 11.12 s and clears the first 60 ft in 2.96 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Opel Omega Sedan 2.5i V6 170 have?
168 bhp and 1,600 kg, which is 105 bhp per tonne. It is rear-drive, naturally aspirated, with 5 gears and a quoted top speed of 228 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Opel Omega Sedan 2.5i V6 170?
Closest here on pace: Holden Vectra Sedan 2.2 147 (8.67 s), Volvo S80 2.0 D4 163 (8.70 s), Renault Vel Satis 2.0 16V Turbo 170 (8.67 s). Each one can be raced against the Opel Omega Sedan 2.5i V6 170 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 Omega Sedan 2.5i V6 170 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.