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

Renault Fluence 2.0 140

The Renault Fluence 2.0 140 reaches 60 mph in 8.52 s (100 km/h in 9.53 s) and covers a standing quarter mile in 16.71 s, tripping the lights at 83.4 mph. It clears the first 60 ft in 2.62 s and the eighth mile in 10.82 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.

Renault Fluence 2.0 140 Ford Mondeo Sedan 2.0 145

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 Renault Fluence 2.0 140
0–60 mph8.52 s
0–100 km/h9.53 s
0–100 mph—
60 ft2.62 s
1/8 mile10.82 s
1/4 mile16.71 s
Trap speed83.4 mph

About the Fluence 2.0 140

The 2009 Renault Fluence 2.0 140 is a front-drive naturally aspirated saloon of 1,260 kg with 138 bhp, which works out at 110 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.62 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,537th quickest to 60 mph, and the 95th quickest of the 499 Renaults here. Its 83.4 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 Renault Fluence 2.0 140
Year2009
Power138 hp (103 kW)
Kerb mass1,260 kg
Power to weight110 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ford Mondeo Sedan 2.0 14520008.48 s16.76 s85.5 mph143 bhp
Opel Omega Sedan 2.6i 15019868.48 s16.76 s85.5 mph148 bhp
BMW 320i E9020058.49 s16.61 s86.0 mph148 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.

Head to head

Renault Megane Estate 2.0 TCe 220 vs Renault Fluence 2.0 140Full comparison

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
Renault 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 Renault Fluence 2.0 140 0-60 time?
The Renault Fluence 2.0 140 reaches 60 mph in 8.52 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,537th quickest of the 14,946 cars in the set.
What is the Renault Fluence 2.0 140 quarter mile time?
16.71 s at 83.4 mph. It reaches the eighth mile in 10.82 s and clears the first 60 ft in 2.62 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Renault Fluence 2.0 140 have?
138 bhp and 1,260 kg, which is 110 bhp per tonne. It is front-drive, naturally aspirated, 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 Renault Fluence 2.0 140?
Closest here on pace: Ford Mondeo Sedan 2.0 145 (8.48 s), Opel Omega Sedan 2.6i 150 (8.48 s), BMW 320i E90 (8.49 s). Each one can be raced against the Renault Fluence 2.0 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 Renault Fluence 2.0 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.