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

Chevrolet Epica 2.5 156

The Chevrolet Epica 2.5 156 reaches 60 mph in 8.98 s (100 km/h in 9.52 s) and covers a standing quarter mile in 16.97 s, tripping the lights at 84.7 mph. It clears the first 60 ft in 2.98 s and the eighth mile in 11.14 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.

Chevrolet Epica 2.5 156 Daewoo Tosca 2.5 160

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 Chevrolet Epica 2.5 156
0–60 mph8.98 s
0–100 km/h9.52 s
0–100 mph—
60 ft2.98 s
1/8 mile11.14 s
1/4 mile16.97 s
Trap speed84.7 mph

About the Epica 2.5 156

The 2006 Chevrolet Epica 2.5 156 is a front-drive naturally aspirated saloon of 1,495 kg with 154 bhp, which works out at 103 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.98 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 8,395th quickest to 60 mph, and the 118th quickest of the 199 Chevrolets here. It traps higher than its 0-60 suggests — 84.7 mph, the 7,466th 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 Chevrolet Epica 2.5 156
Year2006
Power154 hp (115 kW)
Kerb mass1,495 kg
Power to weight103 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed128 mph (206 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Daewoo Tosca 2.5 16020068.98 s16.97 s84.7 mph157 bhp
Holden Epica 2.5 15520078.95 s16.96 s83.2 mph154 bhp
Alfa Romeo 159 Sportwagon 1.9 JTS 16020069.00 s16.97 s83.9 mph158 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
Chevrolet 0-60 timesevery modelFastest saloon cars3,808 carsFastest cars of the 2000s5,138 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 Chevrolet Epica 2.5 156 0-60 time?
The Chevrolet Epica 2.5 156 reaches 60 mph in 8.98 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,395th quickest of the 14,946 cars in the set.
What is the Chevrolet Epica 2.5 156 quarter mile time?
16.97 s at 84.7 mph. It reaches the eighth mile in 11.14 s and clears the first 60 ft in 2.98 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Epica 2.5 156 have?
154 bhp and 1,495 kg, which is 103 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 206 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Epica 2.5 156?
Closest here on pace: Daewoo Tosca 2.5 160 (8.98 s), Holden Epica 2.5 155 (8.95 s), Alfa Romeo 159 Sportwagon 1.9 JTS 160 (9.00 s). Each one can be raced against the Chevrolet Epica 2.5 156 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 Chevrolet Epica 2.5 156 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.