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

Caterham 7 CSR 260

The Caterham 7 CSR 260 reaches 60 mph in 3.55 s (100 km/h in 3.69 s) and covers a standing quarter mile in 11.77 s, tripping the lights at 116.0 mph. It clears the first 60 ft in 1.71 s and the eighth mile in 7.53 s, reaching 100 mph in 8.06 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.

Caterham 7 CSR 260 Caterham Seven 620R

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 Caterham 7 CSR 260
0–60 mph3.55 s
0–100 km/h3.69 s
0–100 mph8.06 s
60 ft1.71 s
1/8 mile7.53 s
1/4 mile11.77 s
Trap speed116.0 mph

About the 7 CSR 260

The 2005 Caterham 7 CSR 260 is a rear-drive naturally aspirated car of 530 kg with 256 bhp, which works out at 483 bhp per tonne. Rear drive and 483 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.71 s. Against the 14,946 cars in the set it is the 685th quickest to 60 mph, inside the fastest five per cent, and the 4th quickest of the 14 Caterhams here. Its 116.0 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 9 of 10 published acceleration figures for this car.

On paper

Specification Caterham 7 CSR 260
Year2005
Power256 hp (191 kW)
Kerb mass530 kg
Power to weight483 bhp/t
DrivetrainRear drive
Gears6
EngineNaturally aspirated
Top speed157 mph (252 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Caterham Seven 620R20133.46 s11.73 s114.7 mph310 bhp
Dodge SRT Viper 8.4 V10 65020123.50 s11.60 s124.9 mph640 bhp
Marcos TSO GT220063.63 s11.79 s120.8 mph468 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.

Head to head

Lotus Elise 1.6 vs Caterham 7 CSR 260Full comparison

Where these times sit

0-60 under 4 seconds1,060 cars0-100 km/h under 4 seconds881 carsQuarter mile under 12 seconds780 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
Caterham 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 Caterham 7 CSR 260 0-60 time?
The Caterham 7 CSR 260 reaches 60 mph in 3.55 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 685th quickest of the 14,946 cars in the set.
What is the Caterham 7 CSR 260 quarter mile time?
11.77 s at 116.0 mph. It reaches the eighth mile in 7.53 s and clears the first 60 ft in 1.71 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Caterham 7 CSR 260 have?
256 bhp and 530 kg, which is 483 bhp per tonne. It is rear-drive, naturally aspirated, with 6 gears and a quoted top speed of 252 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Caterham 7 CSR 260?
Closest here on pace: Caterham Seven 620R (3.46 s), Dodge SRT Viper 8.4 V10 650 (3.50 s), Marcos TSO GT2 (3.63 s). Each one can be raced against the Caterham 7 CSR 260 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 Caterham 7 CSR 260 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 of its 10 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.