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

Fiat Bravo 2.0 Multijet 165

The Fiat Bravo 2.0 Multijet 165 reaches 60 mph in 7.42 s (100 km/h in 7.84 s) and covers a standing quarter mile in 15.80 s, tripping the lights at 88.3 mph. It clears the first 60 ft in 2.46 s and the eighth mile in 10.25 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.

Fiat Bravo 2.0 Multijet 165 Alfa Romeo MiTo 1.4 Turbo MultiAir 140

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 Fiat Bravo 2.0 Multijet 165
0–60 mph7.42 s
0–100 km/h7.84 s
0–100 mph—
60 ft2.46 s
1/8 mile10.25 s
1/4 mile15.80 s
Trap speed88.3 mph

About the Bravo 2.0 Multijet 165

The 2007 Fiat Bravo 2.0 Multijet 165 is a front-drive turbodiesel car of 1,335 kg with 162 bhp, which works out at 122 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.46 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 5,399th quickest to 60 mph, and the 28th quickest of the 455 Fiats here. Its 88.3 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 Fiat Bravo 2.0 Multijet 165
Year2007
Power162 hp (121 kW)
Kerb mass1,335 kg
Power to weight122 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed133 mph (214 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Alfa Romeo MiTo 1.4 Turbo MultiAir 14020137.42 s15.83 s88.4 mph138 bhp
VW Golf VII 3dr 1.4 TSI 15020177.43 s15.78 s88.3 mph148 bhp
VW Golf VII 5dr 1.4 TSI 15020177.43 s15.78 s88.3 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.

Where these times sit

0-60 under 8 seconds6,514 cars0-100 km/h under 8 seconds5,602 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Fiat 0-60 timesevery modelFastest diesel cars4,019 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 Fiat Bravo 2.0 Multijet 165 0-60 time?
The Fiat Bravo 2.0 Multijet 165 reaches 60 mph in 7.42 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,399th quickest of the 14,946 cars in the set.
What is the Fiat Bravo 2.0 Multijet 165 quarter mile time?
15.80 s at 88.3 mph. It reaches the eighth mile in 10.25 s and clears the first 60 ft in 2.46 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Fiat Bravo 2.0 Multijet 165 have?
162 bhp and 1,335 kg, which is 122 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 214 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Fiat Bravo 2.0 Multijet 165?
Closest here on pace: Alfa Romeo MiTo 1.4 Turbo MultiAir 140 (7.42 s), VW Golf VII 3dr 1.4 TSI 150 (7.43 s), VW Golf VII 5dr 1.4 TSI 150 (7.43 s). Each one can be raced against the Fiat Bravo 2.0 Multijet 165 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 Fiat Bravo 2.0 Multijet 165 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.