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

Chevrolet Trailblazer 2.5 CDTI 150

The Chevrolet Trailblazer 2.5 CDTI 150 reaches 60 mph in 9.77 s (100 km/h in 10.39 s) and covers a standing quarter mile in 17.38 s, tripping the lights at 78.9 mph. It clears the first 60 ft in 2.70 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.

Chevrolet Trailblazer 2.5 CDTI 150 Hyundai Ioniq 1.6 105

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 Trailblazer 2.5 CDTI 150
0–60 mph9.77 s
0–100 km/h10.39 s
0–100 mph—
60 ft2.70 s
1/8 mile11.12 s
1/4 mile17.38 s
Trap speed78.9 mph

About the Trailblazer 2.5 CDTI 150

The 2012 Chevrolet Trailblazer 2.5 CDTI 150 is a front-drive turbodiesel saloon of 1,971 kg with 148 bhp, which works out at 75 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.70 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 9,740th quickest to 60 mph, and the 130th quickest of the 199 Chevrolets here. Its 78.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 Chevrolet Trailblazer 2.5 CDTI 150
Year2012
Power148 hp (110 kW)
Kerb mass1,971 kg
Power to weight75 bhp/t
DrivetrainFront drive
Gears5
EngineTurbodiesel
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Hyundai Ioniq 1.6 10520209.74 s17.37 s79.5 mph103 bhp
Hyundai Ioniq 1.6 14120169.74 s17.37 s79.5 mph105 bhp
Skoda Octavia 1.4 G-TEC 11020179.73 s17.33 s78.9 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

0-60 under 10 seconds10,136 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 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 Chevrolet Trailblazer 2.5 CDTI 150 0-60 time?
The Chevrolet Trailblazer 2.5 CDTI 150 reaches 60 mph in 9.77 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,740th quickest of the 14,946 cars in the set.
What is the Chevrolet Trailblazer 2.5 CDTI 150 quarter mile time?
17.38 s at 78.9 mph. It reaches the eighth mile in 11.12 s and clears the first 60 ft in 2.70 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Trailblazer 2.5 CDTI 150 have?
148 bhp and 1,971 kg, which is 75 bhp per tonne. It is front-drive, turbodiesel, with 5 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Trailblazer 2.5 CDTI 150?
Closest here on pace: Hyundai Ioniq 1.6 105 (9.74 s), Hyundai Ioniq 1.6 141 (9.74 s), Skoda Octavia 1.4 G-TEC 110 (9.73 s). Each one can be raced against the Chevrolet Trailblazer 2.5 CDTI 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 Chevrolet Trailblazer 2.5 CDTI 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.