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

Ford GT 3.5 V6 660

The Ford GT 3.5 V6 660 reaches 60 mph in 2.73 s (100 km/h in 2.83 s) and covers a standing quarter mile in 10.25 s, tripping the lights at 140.2 mph. It clears the first 60 ft in 1.64 s and the eighth mile in 6.69 s, reaching 100 mph in 5.51 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.

Ford GT 3.5 V6 660 Ferrari F12 TRS 6.3 V12 740

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 Ford GT 3.5 V6 660
0–60 mph2.73 s
0–100 km/h2.83 s
0–100 mph5.51 s
60 ft1.64 s
1/8 mile6.69 s
1/4 mile10.25 s
Trap speed140.2 mph

About the GT 3.5 V6 660

The 2019 Ford GT 3.5 V6 660 is a rear-drive turbocharged coupe of 1,385 kg with 650 bhp, which works out at 470 bhp per tonne. Rear drive and 470 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.64 s. Against the 14,946 cars in the set it is the 170th quickest to 60 mph, inside the fastest five per cent, and the quickest of the 789 Fords here. Its 140.2 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 Ford GT 3.5 V6 660
Year2019
Power650 hp (485 kW)
Kerb mass1,385 kg
Power to weight470 bhp/t
DrivetrainRear drive
Gears7
EngineTurbocharged
Top speed216 mph (348 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ferrari F12 TRS 6.3 V12 74020142.72 s10.33 s138.2 mph730 bhp
Ferrari 812 GTS 6.5 V12 80020192.64 s10.11 s140.0 mph789 bhp
Mclaren 620R 3.8 V8 62020192.53 s10.27 s134.9 mph612 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

Chevrolet Corvette C8 Stingray vs Ford GT 3.5 V6 660Full comparison

Where these times sit

0-60 under 3 seconds271 cars0-100 km/h under 3 seconds213 carsQuarter mile under 11 seconds272 cars0-100 under 7 seconds311 carsTraps over 140 mph108 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Ford 0-60 timesevery modelFastest supercars629 carsFastest cars of the 2010s4,541 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 Ford GT 3.5 V6 660 0-60 time?
The Ford GT 3.5 V6 660 reaches 60 mph in 2.73 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 170th quickest of the 14,946 cars in the set.
What is the Ford GT 3.5 V6 660 quarter mile time?
10.25 s at 140.2 mph. It reaches the eighth mile in 6.69 s and clears the first 60 ft in 1.64 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ford GT 3.5 V6 660 have?
650 bhp and 1,385 kg, which is 470 bhp per tonne. It is rear-drive, turbocharged, with 7 gears and a quoted top speed of 348 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ford GT 3.5 V6 660?
Closest here on pace: Ferrari F12 TRS 6.3 V12 740 (2.72 s), Ferrari 812 GTS 6.5 V12 800 (2.64 s), Mclaren 620R 3.8 V8 620 (2.53 s). Each one can be raced against the Ford GT 3.5 V6 660 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 Ford GT 3.5 V6 660 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.