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

Ferrari California GT

The Ferrari California GT reaches 60 mph in 3.73 s (100 km/h in 3.89 s) and covers a standing quarter mile in 12.09 s, tripping the lights at 118.5 mph. It clears the first 60 ft in 1.93 s and the eighth mile in 7.84 s, reaching 100 mph in 9.05 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 California GT Jaguar F-Pace SVR

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 California GT
0–60 mph3.73 s
0–100 km/h3.89 s
0–100 mph9.05 s
60 ft1.93 s
1/8 mile7.84 s
1/4 mile12.09 s
Trap speed118.5 mph

About the California GT

The 2009 Ferrari California GT is a rear-drive naturally aspirated saloon of 1,787 kg with 453 bhp, which works out at 254 bhp per tonne. Rear drive and 254 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.93 s. Against the 14,946 cars in the set it is the 823rd quickest to 60 mph, inside the fastest tenth, and the 57th quickest of the 129 Ferraris here. Its 118.5 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 9 of 11 published acceleration figures for this car.

On paper

Specification Ferrari California GT
Year2009
Power453 hp (338 kW)
Kerb mass1,787 kg
Power to weight254 bhp/t
DrivetrainRear drive
Gears6
EngineNaturally aspirated
Top speed194 mph (312 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Jaguar F-Pace SVR20193.72 s12.10 s116.1 mph543 bhp
Maserati Levante GTS 3.8 V8 55020163.73 s12.19 s114.2 mph543 bhp
Mercedes-AMG S 65 L (V222) 6.0 V12 63020173.76 s12.07 s114.7 mph621 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 4 seconds1,060 cars0-100 km/h under 4 seconds881 carsQuarter mile under 13 seconds1,638 cars0-100 under 12 seconds1,963 carsTraps over 110 mph1,380 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 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 Ferrari California GT 0-60 time?
The Ferrari California GT reaches 60 mph in 3.73 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 823rd quickest of the 14,946 cars in the set.
What is the Ferrari California GT quarter mile time?
12.09 s at 118.5 mph. It reaches the eighth mile in 7.84 s and clears the first 60 ft in 1.93 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ferrari California GT have?
453 bhp and 1,787 kg, which is 254 bhp per tonne. It is rear-drive, naturally aspirated, with 6 gears and a quoted top speed of 312 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ferrari California GT?
Closest here on pace: Jaguar F-Pace SVR (3.72 s), Maserati Levante GTS 3.8 V8 550 (3.73 s), Mercedes-AMG S 65 L (V222) 6.0 V12 630 (3.76 s). Each one can be raced against the Ferrari California GT 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 California GT is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 of its 11 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.