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

TVR Tuscan 3.6 350

The TVR Tuscan 3.6 350 reaches 60 mph in 3.97 s (100 km/h in 4.14 s) and covers a standing quarter mile in 12.15 s, tripping the lights at 116.5 mph. It clears the first 60 ft in 2.05 s and the eighth mile in 7.93 s, reaching 100 mph in 8.76 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.

TVR Tuscan 3.6 350 Aston Martin V12 Vantage Mk I

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 TVR Tuscan 3.6 350
0–60 mph3.97 s
0–100 km/h4.14 s
0–100 mph8.76 s
60 ft2.05 s
1/8 mile7.93 s
1/4 mile12.15 s
Trap speed116.5 mph

About the Tuscan 3.6 350

The 2001 TVR Tuscan 3.6 350 is a rear-drive naturally aspirated coupe of 1,100 kg with 345 bhp, which works out at 313 bhp per tonne. Rear drive and 313 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.05 s. Against the 14,946 cars in the set it is the 1,041st quickest to 60 mph, inside the fastest tenth, and the 21st quickest of the 32 TVRs here. Its 116.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 2 of 2 published acceleration figures for this car.

On paper

Specification TVR Tuscan 3.6 350
Year2001
Power345 hp (257 kW)
Kerb mass1,100 kg
Power to weight313 bhp/t
DrivetrainRear drive
Gears5
EngineNaturally aspirated
Top speed175 mph (282 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Aston Martin V12 Vantage Mk I20093.94 s12.18 s120.2 mph510 bhp
Morgan AeroMax 4.8 V8 36820053.97 s12.12 s115.2 mph333 bhp
Wiesmann GT MF4-CS 4.0 V8 42020133.92 s12.32 s114.8 mph414 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 5 seconds1,845 carsQuarter mile under 13 seconds1,638 cars0-100 under 9 seconds871 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
TVR 0-60 timesevery modelFastest supercars629 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 TVR Tuscan 3.6 350 0-60 time?
The TVR Tuscan 3.6 350 reaches 60 mph in 3.97 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 1,041st quickest of the 14,946 cars in the set.
What is the TVR Tuscan 3.6 350 quarter mile time?
12.15 s at 116.5 mph. It reaches the eighth mile in 7.93 s and clears the first 60 ft in 2.05 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the TVR Tuscan 3.6 350 have?
345 bhp and 1,100 kg, which is 313 bhp per tonne. It is rear-drive, naturally aspirated, with 5 gears and a quoted top speed of 282 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the TVR Tuscan 3.6 350?
Closest here on pace: Aston Martin V12 Vantage Mk I (3.94 s), Morgan AeroMax 4.8 V8 368 (3.97 s), Wiesmann GT MF4-CS 4.0 V8 420 (3.92 s). Each one can be raced against the TVR Tuscan 3.6 350 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 TVR Tuscan 3.6 350 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.