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

Chevrolet Orlando 1.4 Turbo 140

The Chevrolet Orlando 1.4 Turbo 140 reaches 60 mph in 9.49 s (100 km/h in 10.59 s) and covers a standing quarter mile in 17.27 s, tripping the lights at 80.8 mph. It clears the first 60 ft in 2.63 s and the eighth mile in 11.11 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 Orlando 1.4 Turbo 140 SEAT Alhambra 1.4 TSI 150

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 Orlando 1.4 Turbo 140
0–60 mph9.49 s
0–100 km/h10.59 s
0–100 mph—
60 ft2.63 s
1/8 mile11.11 s
1/4 mile17.27 s
Trap speed80.8 mph

About the Orlando 1.4 Turbo 140

The 2010 Chevrolet Orlando 1.4 Turbo 140 is a front-drive turbocharged MPV of 1,539 kg with 138 bhp, which works out at 90 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.63 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,276th quickest to 60 mph, and the 125th quickest of the 199 Chevrolets here. Its 80.8 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 Orlando 1.4 Turbo 140
Year2010
Power138 hp (103 kW)
Kerb mass1,539 kg
Power to weight90 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
SEAT Alhambra 1.4 TSI 15020109.45 s17.20 s79.9 mph148 bhp
Citroen C8 2.2 HDi Biturbo 17020089.58 s17.16 s80.0 mph168 bhp
Renault Scenic 1.6 dCi 13020099.57 s17.04 s80.8 mph129 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 MPVs and people carriers478 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 Orlando 1.4 Turbo 140 0-60 time?
The Chevrolet Orlando 1.4 Turbo 140 reaches 60 mph in 9.49 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,276th quickest of the 14,946 cars in the set.
What is the Chevrolet Orlando 1.4 Turbo 140 quarter mile time?
17.27 s at 80.8 mph. It reaches the eighth mile in 11.11 s and clears the first 60 ft in 2.63 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Chevrolet Orlando 1.4 Turbo 140 have?
138 bhp and 1,539 kg, which is 90 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 200 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Chevrolet Orlando 1.4 Turbo 140?
Closest here on pace: SEAT Alhambra 1.4 TSI 150 (9.45 s), Citroen C8 2.2 HDi Biturbo 170 (9.58 s), Renault Scenic 1.6 dCi 130 (9.57 s). Each one can be raced against the Chevrolet Orlando 1.4 Turbo 140 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 Orlando 1.4 Turbo 140 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.