← My Auto Racer All cars Lexus 0-60 Comparisons Answers
The Lexus CT 200H reaches 60 mph in 10.19 s and covers a standing quarter mile in 17.85 s, tripping the lights at 80.5 mph. It clears the first 60 ft in 3.02 s and the eighth mile in 11.73 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Lexus CT 200H |
|---|---|
| 0–60 mph | 10.19 s |
| 0–100 mph | — |
| 60 ft | 3.02 s |
| 1/8 mile | 11.73 s |
| 1/4 mile | 17.85 s |
| Trap speed | 80.5 mph |
The 2011 Lexus CT 200H is a front-drive turbocharged car of 1,499 kg with 161 bhp, which works out at 107 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.02 s — so most of what it has to give arrives once it is already moving. Against the 2,939 cars in the set it is the 2,886th quickest to 60 mph, and the 29th quickest of the 29 Lexuss here. Its 80.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 8 of 9 published acceleration figures for this car.
| Specification | Lexus CT 200H |
|---|---|
| Year | 2011 |
| Power | 161 bhp |
| Kerb mass | 1,499 kg |
| Power to weight | 107 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 182 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Citroen DS3 HDI 110 FAP | 2010 | 10.02 s | 17.49 s | 78.0 mph | 110 bhp |
| Nissan Versa 1.6 N17 | 2011 | 10.56 s | 17.87 s | 77.4 mph | 109 bhp |
| De Lorean DMC-12 USA spec | 1978 | 9.84 s | 17.75 s | 82.3 mph | 129 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.
Figures regenerated 2026-09-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.