← My Auto Racer All cars Vector 0-60 Comparisons
The Vector M12 reaches 60 mph in 3.95 s and covers a standing quarter mile in 12.25 s, tripping the lights at 118.7 mph. It clears the first 60 ft in 2.00 s and the eighth mile in 8.00 s, reaching 100 mph in 9.20 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 | Vector M12 |
|---|---|
| 0–60 mph | 3.95 s |
| 0–100 mph | 9.20 s |
| 60 ft | 2.00 s |
| 1/8 mile | 8.00 s |
| 1/4 mile | 12.25 s |
| Trap speed | 118.7 mph |
The 1996 Vector M12 is a rear-drive naturally aspirated car of 1,635 kg with 485 bhp, which works out at 297 bhp per tonne. Rear drive and 297 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.00 s. Against the 2,929 cars in the set it is the 768th quickest to 60 mph, and the 2nd quickest of the 2 Vectors here. It traps higher than its 0-60 suggests — 118.7 mph, the 576th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 9 of 11 published acceleration figures for this car.
| Specification | Vector M12 |
|---|---|
| Year | 1996 |
| Power | 485 bhp |
| Kerb mass | 1,635 kg |
| Power to weight | 297 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 308 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Lotus Evora 400 | 2016 | 3.96 s | 12.33 s | 115.0 mph | 400 bhp |
| Panoz Esperante GTLM | 2006 | 3.81 s | 12.38 s | 114.4 mph | 414 bhp |
| Shelby Series 1 | 1998 | 4.00 s | 12.67 s | 111.0 mph | 321 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-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.