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

Acura NSX-T 3.2 V6 240

The Acura NSX-T 3.2 V6 240 reaches 60 mph in 5.16 s (100 km/h in 5.40 s) and covers a standing quarter mile in 13.39 s, tripping the lights at 107.5 mph. It clears the first 60 ft in 2.15 s and the eighth mile in 8.72 s, reaching 100 mph in 11.74 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.

Acura NSX-T 3.2 V6 240 Ferrari 348 tb 3.4 V8 300

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 Acura NSX-T 3.2 V6 240
0–60 mph5.16 s
0–100 km/h5.40 s
0–100 mph11.74 s
60 ft2.15 s
1/8 mile8.72 s
1/4 mile13.39 s
Trap speed107.5 mph

About the NSX-T 3.2 V6 240

The 2001 Acura NSX-T 3.2 V6 240 is a rear-drive naturally aspirated coupe of 1,392 kg with 286 bhp, which works out at 205 bhp per tonne. Rear drive and 205 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.15 s. Against the 14,946 cars in the set it is the 2,318th quickest to 60 mph, inside the fastest quarter, and the 2nd quickest of the 25 Acuras here. Its 107.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 Acura NSX-T 3.2 V6 240
Year2001
Power286 hp (213 kW)
Kerb mass1,392 kg
Power to weight205 bhp/t
DrivetrainRear drive
Gears6
EngineNaturally aspirated
Top speed168 mph (270 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ferrari 348 tb 3.4 V8 30019895.08 s13.38 s108.0 mph295 bhp
Ferrari 348 ts 3.4 V8 30019895.08 s13.38 s108.0 mph296 bhp
Jaguar F-Type Coupe20145.14 s13.46 s105.0 mph335 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 6 seconds3,249 cars0-100 km/h under 6 seconds2,894 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
Acura 0-60 timesevery modelFastest coupes911 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 Acura NSX-T 3.2 V6 240 0-60 time?
The Acura NSX-T 3.2 V6 240 reaches 60 mph in 5.16 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 2,318th quickest of the 14,946 cars in the set.
What is the Acura NSX-T 3.2 V6 240 quarter mile time?
13.39 s at 107.5 mph. It reaches the eighth mile in 8.72 s and clears the first 60 ft in 2.15 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Acura NSX-T 3.2 V6 240 have?
286 bhp and 1,392 kg, which is 205 bhp per tonne. It is rear-drive, naturally aspirated, with 6 gears and a quoted top speed of 270 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Acura NSX-T 3.2 V6 240?
Closest here on pace: Ferrari 348 tb 3.4 V8 300 (5.08 s), Ferrari 348 ts 3.4 V8 300 (5.08 s), Jaguar F-Type Coupe (5.14 s). Each one can be raced against the Acura NSX-T 3.2 V6 240 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 Acura NSX-T 3.2 V6 240 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.