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

Ferrari Mondial 3.2 3.2 V8 260

The Ferrari Mondial 3.2 3.2 V8 260 reaches 60 mph in 6.92 s (100 km/h in 7.24 s) and covers a standing quarter mile in 15.31 s, tripping the lights at 96.6 mph. It clears the first 60 ft in 2.71 s and the eighth mile in 10.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.

Ferrari Mondial 3.2 3.2 V8 260 Acura NSX-T 3.0 V6 252

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 Ferrari Mondial 3.2 3.2 V8 260
0–60 mph6.92 s
0–100 km/h7.24 s
0–100 mph—
60 ft2.71 s
1/8 mile10.12 s
1/4 mile15.31 s
Trap speed96.6 mph

About the Mondial 3.2 3.2 V8 260

The 1985 Ferrari Mondial 3.2 3.2 V8 260 is a rear-drive naturally aspirated coupe of 1,540 kg with 260 bhp, which works out at 169 bhp per tonne. Rear drive and 169 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.71 s. Against the 14,946 cars in the set it is the 4,508th quickest to 60 mph, and the 114th quickest of the 129 Ferraris here. It traps higher than its 0-60 suggests — 96.6 mph, the 3,341st highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Ferrari Mondial 3.2 3.2 V8 260
Year1985
Power260 hp (194 kW)
Kerb mass1,540 kg
Power to weight169 bhp/t
DrivetrainRear drive
Gears5
EngineNaturally aspirated
Top speed152 mph (245 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Acura NSX-T 3.0 V6 25220016.89 s15.15 s101.6 mph248 bhp
Morgan Plus 4 2.020056.82 s15.19 s93.2 mph143 bhp
Maserati Merak 3.0 V6 SS 21019747.02 s15.37 s96.5 mph208 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 7 seconds4,651 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
Ferrari 0-60 timesevery modelFastest coupes911 carsFastest cars of the 1980s1,057 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 Ferrari Mondial 3.2 3.2 V8 260 0-60 time?
The Ferrari Mondial 3.2 3.2 V8 260 reaches 60 mph in 6.92 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,508th quickest of the 14,946 cars in the set.
What is the Ferrari Mondial 3.2 3.2 V8 260 quarter mile time?
15.31 s at 96.6 mph. It reaches the eighth mile in 10.12 s and clears the first 60 ft in 2.71 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ferrari Mondial 3.2 3.2 V8 260 have?
260 bhp and 1,540 kg, which is 169 bhp per tonne. It is rear-drive, naturally aspirated, with 5 gears and a quoted top speed of 245 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ferrari Mondial 3.2 3.2 V8 260?
Closest here on pace: Acura NSX-T 3.0 V6 252 (6.89 s), Morgan Plus 4 2.0 (6.82 s), Maserati Merak 3.0 V6 SS 210 (7.02 s). Each one can be raced against the Ferrari Mondial 3.2 3.2 V8 260 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 Ferrari Mondial 3.2 3.2 V8 260 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.