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

Ruf RT 35 Roadster

The Ruf RT 35 Roadster reaches 60 mph in 2.90 s (100 km/h in 3.02 s) and covers a standing quarter mile in 10.87 s, tripping the lights at 130.7 mph. It clears the first 60 ft in 1.66 s and the eighth mile in 7.02 s, reaching 100 mph in 6.49 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.

Ruf RT 35 Roadster Mclaren 570GT

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 Ruf RT 35 Roadster
0–60 mph2.90 s
0–100 km/h3.02 s
0–100 mph6.49 s
60 ft1.66 s
1/8 mile7.02 s
1/4 mile10.87 s
Trap speed130.7 mph

About the RT 35 Roadster

The 2013 Ruf RT 35 Roadster is an all-wheel-drive turbocharged supercar of 1,640 kg with 621 bhp, which works out at 379 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 1.66 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 234th quickest to 60 mph, inside the fastest five per cent, and the 3rd quickest of the 23 Rufs here. Its 130.7 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 11 of 11 published acceleration figures for this car.

On paper

Specification Ruf RT 35 Roadster
Year2013
Power621 hp (463 kW)
Kerb mass1,640 kg
Power to weight379 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbocharged
Top speed210 mph (338 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mclaren 570GT20162.90 s10.67 s133.8 mph562 bhp
Lamborghini Huracan Spyder20172.97 s10.92 s129.9 mph602 bhp
Ferrari Roma Spider Tipo F16920232.87 s10.75 s131.5 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.

Where these times sit

0-60 under 3 seconds271 cars0-100 km/h under 4 seconds881 carsQuarter mile under 11 seconds272 cars0-100 under 7 seconds311 carsTraps over 130 mph250 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Ruf 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 Ruf RT 35 Roadster 0-60 time?
The Ruf RT 35 Roadster reaches 60 mph in 2.90 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 234th quickest of the 14,946 cars in the set.
What is the Ruf RT 35 Roadster quarter mile time?
10.87 s at 130.7 mph. It reaches the eighth mile in 7.02 s and clears the first 60 ft in 1.66 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ruf RT 35 Roadster have?
621 bhp and 1,640 kg, which is 379 bhp per tonne. It is all-wheel-drive, turbocharged, with 6 gears and a quoted top speed of 338 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ruf RT 35 Roadster?
Closest here on pace: Mclaren 570GT (2.90 s), Lamborghini Huracan Spyder (2.97 s), Ferrari Roma Spider Tipo F169 (2.87 s). Each one can be raced against the Ruf RT 35 Roadster 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 Ruf RT 35 Roadster is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 11 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-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.