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

Smart Roadster Coupe Brabus 0.7 101

The Smart Roadster Coupe Brabus 0.7 101 reaches 60 mph in 8.83 s (100 km/h in 9.40 s) and covers a standing quarter mile in 16.65 s, tripping the lights at 81.6 mph. It clears the first 60 ft in 2.49 s and the eighth mile in 10.63 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.

Smart Roadster Coupe Brabus 0.7 101 Mazda MX-5 1.6 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 Smart Roadster Coupe Brabus 0.7 101
0–60 mph8.83 s
0–100 km/h9.40 s
0–100 mph—
60 ft2.49 s
1/8 mile10.63 s
1/4 mile16.65 s
Trap speed81.6 mph

About the Roadster Coupe Brabus 0.7 101

The 2003 Smart Roadster Coupe Brabus 0.7 101 is a rear-drive turbocharged roadster of 852 kg with 99 bhp, which works out at 116 bhp per tonne. Rear drive and 116 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.49 s. Against the 14,946 cars in the set it is the 8,087th quickest to 60 mph, and the 13th quickest of the 24 Smarts here. It leaves better than it pulls: 81.6 mph at the lights is only the 9,157th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Smart Roadster Coupe Brabus 0.7 101
Year2003
Power99 hp (74 kW)
Kerb mass852 kg
Power to weight116 bhp/t
DrivetrainRear drive
Gears6
EngineTurbocharged
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mazda MX-5 1.6 Mk I19908.81 s16.74 s84.0 mph115 bhp
Saab 900 Cabrio 2.0 Turbo 16019868.72 s16.53 s83.5 mph158 bhp
BMW Z3 1.919968.89 s16.98 s84.3 mph138 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 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Smart 0-60 timesevery modelFastest roadsters682 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 Smart Roadster Coupe Brabus 0.7 101 0-60 time?
The Smart Roadster Coupe Brabus 0.7 101 reaches 60 mph in 8.83 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,087th quickest of the 14,946 cars in the set.
What is the Smart Roadster Coupe Brabus 0.7 101 quarter mile time?
16.65 s at 81.6 mph. It reaches the eighth mile in 10.63 s and clears the first 60 ft in 2.49 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Smart Roadster Coupe Brabus 0.7 101 have?
99 bhp and 852 kg, which is 116 bhp per tonne. It is rear-drive, turbocharged, with 6 gears and a quoted top speed of 195 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Smart Roadster Coupe Brabus 0.7 101?
Closest here on pace: Mazda MX-5 1.6 Mk I (8.81 s), Saab 900 Cabrio 2.0 Turbo 160 (8.72 s), BMW Z3 1.9 (8.89 s). Each one can be raced against the Smart Roadster Coupe Brabus 0.7 101 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 Smart Roadster Coupe Brabus 0.7 101 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.