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

Ferrari F355 Spider

The Ferrari F355 Spider reaches 60 mph in 4.54 s (100 km/h in 4.75 s) and covers a standing quarter mile in 13.15 s, tripping the lights at 108.4 mph. It clears the first 60 ft in 2.13 s and the eighth mile in 8.53 s, reaching 100 mph in 11.38 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 F355 Spider Jaguar XKR (2006)

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 F355 Spider
0–60 mph4.54 s
0–100 km/h4.75 s
0–100 mph11.38 s
60 ft2.13 s
1/8 mile8.53 s
1/4 mile13.15 s
Trap speed108.4 mph

About the F355 Spider

The 1995 Ferrari F355 Spider is a rear-drive naturally aspirated roadster of 1,512 kg with 375 bhp, which works out at 248 bhp per tonne. Rear drive and 248 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.13 s. Against the 14,946 cars in the set it is the 1,685th quickest to 60 mph, inside the fastest quarter, and the 69th quickest of the 129 Ferraris here. Its 108.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 10 of 10 published acceleration figures for this car.

On paper

Specification Ferrari F355 Spider
Year1995
Power375 hp (280 kW)
Kerb mass1,512 kg
Power to weight248 bhp/t
DrivetrainRear drive
Gears6
EngineNaturally aspirated
Top speed183 mph (295 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Jaguar XKR (2006)20064.60 s13.16 s109.7 mph414 bhp
Maserati GranSport Spyder 4.2 GT V8 39020064.50 s13.05 s111.3 mph385 bhp
Maserati Spyder 4.2 V8 GT 39020014.50 s13.05 s111.3 mph385 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 5 seconds2,158 cars0-100 km/h under 5 seconds1,845 carsQuarter mile under 14 seconds2,644 cars0-100 under 12 seconds1,963 carsTraps over 100 mph2,737 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 roadsters682 carsFastest cars of the 1990s2,649 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 F355 Spider 0-60 time?
The Ferrari F355 Spider reaches 60 mph in 4.54 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 1,685th quickest of the 14,946 cars in the set.
What is the Ferrari F355 Spider quarter mile time?
13.15 s at 108.4 mph. It reaches the eighth mile in 8.53 s and clears the first 60 ft in 2.13 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ferrari F355 Spider have?
375 bhp and 1,512 kg, which is 248 bhp per tonne. It is rear-drive, naturally aspirated, with 6 gears and a quoted top speed of 295 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ferrari F355 Spider?
Closest here on pace: Jaguar XKR (2006) (4.60 s), Maserati GranSport Spyder 4.2 GT V8 390 (4.50 s), Maserati Spyder 4.2 V8 GT 390 (4.50 s). Each one can be raced against the Ferrari F355 Spider 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 F355 Spider is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 10 of its 10 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.