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

Proton Preve 1.6 CVT 140

The Proton Preve 1.6 CVT 140 reaches 60 mph in 8.61 s (100 km/h in 9.22 s) and covers a standing quarter mile in 16.68 s, tripping the lights at 81.7 mph. It clears the first 60 ft in 2.56 s and the eighth mile in 10.65 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.

Proton Preve 1.6 CVT 140 Renault Talisman 1.6 TCe 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 Proton Preve 1.6 CVT 140
0–60 mph8.61 s
0–100 km/h9.22 s
0–100 mph—
60 ft2.56 s
1/8 mile10.65 s
1/4 mile16.68 s
Trap speed81.7 mph

About the Preve 1.6 CVT 140

The 2011 Proton Preve 1.6 CVT 140 is a front-drive turbocharged saloon of 1,340 kg with 138 bhp, which works out at 103 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.56 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 7,726th quickest to 60 mph, and the 2nd quickest of the 21 Protons here. It leaves better than it pulls: 81.7 mph at the lights is only the 9,107th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Proton Preve 1.6 CVT 140
Year2011
Power138 hp (103 kW)
Kerb mass1,340 kg
Power to weight103 bhp/t
DrivetrainFront drive
Gears7
EngineTurbocharged
Top speed118 mph (190 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Talisman 1.6 TCe 15020168.65 s16.63 s83.6 mph148 bhp
Vauxhall Insignia Sedan 2.0 CDTI 16020088.60 s16.61 s84.4 mph158 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
Proton 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 Proton Preve 1.6 CVT 140 0-60 time?
The Proton Preve 1.6 CVT 140 reaches 60 mph in 8.61 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,726th quickest of the 14,946 cars in the set.
What is the Proton Preve 1.6 CVT 140 quarter mile time?
16.68 s at 81.7 mph. It reaches the eighth mile in 10.65 s and clears the first 60 ft in 2.56 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Proton Preve 1.6 CVT 140 have?
138 bhp and 1,340 kg, which is 103 bhp per tonne. It is front-drive, turbocharged, with 7 gears and a quoted top speed of 190 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Proton Preve 1.6 CVT 140?
Closest here on pace: Renault Talisman 1.6 TCe 150 (8.65 s), Vauxhall Insignia Sedan 2.0 CDTI 160 (8.60 s), Renault Vel Satis 2.0 16V Turbo 170 (8.67 s). Each one can be raced against the Proton Preve 1.6 CVT 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 Proton Preve 1.6 CVT 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.