← My Auto Racer All cars Comparisons Answers

Ifr Aspid GT-21 Invictus

The Ifr Aspid GT-21 Invictus reaches 60 mph in 2.69 s (100 km/h in 2.80 s) and covers a standing quarter mile in 10.76 s, tripping the lights at 128.5 mph. It clears the first 60 ft in 1.60 s and the eighth mile in 6.94 s, reaching 100 mph in 6.60 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.

Ifr Aspid GT-21 Invictus Ferrari 458 Speciale A

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 Ifr Aspid GT-21 Invictus
0–60 mph2.69 s
0–100 km/h2.80 s
0–100 mph6.60 s
60 ft1.60 s
1/8 mile6.94 s
1/4 mile10.76 s
Trap speed128.5 mph

About the Aspid GT-21 Invictus

The 2012 Ifr Aspid GT-21 Invictus is a rear-drive naturally aspirated supercar of 990 kg with 444 bhp, which works out at 448 bhp per tonne. Rear drive and 448 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.60 s. Against the 14,946 cars in the set it is the 149th quickest to 60 mph, inside the fastest one per cent of the set, and the quickest of the 2 Ifrs here. Its 128.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 10 of 11 published acceleration figures for this car.

On paper

Specification Ifr Aspid GT-21 Invictus
Year2012
Power444 hp (331 kW)
Kerb mass990 kg
Power to weight448 bhp/t
DrivetrainRear drive
Gears6
EngineNaturally aspirated
Top speed190 mph (305 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ferrari 458 Speciale A20142.75 s10.66 s130.8 mph597 bhp
Lamborghini Huracan Evo Epyder 5.2 V10 64020192.74 s10.73 s129.6 mph632 bhp
Mclaren Artura20222.72 s10.46 s134.9 mph691 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 3 seconds213 carsQuarter mile under 11 seconds272 cars0-100 under 7 seconds311 carsTraps over 120 mph651 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Fastest 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 Ifr Aspid GT-21 Invictus 0-60 time?
The Ifr Aspid GT-21 Invictus reaches 60 mph in 2.69 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 149th quickest of the 14,946 cars in the set.
What is the Ifr Aspid GT-21 Invictus quarter mile time?
10.76 s at 128.5 mph. It reaches the eighth mile in 6.94 s and clears the first 60 ft in 1.60 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ifr Aspid GT-21 Invictus have?
444 bhp and 990 kg, which is 448 bhp per tonne. It is rear-drive, naturally aspirated, with 6 gears and a quoted top speed of 305 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ifr Aspid GT-21 Invictus?
Closest here on pace: Ferrari 458 Speciale A (2.75 s), Lamborghini Huracan Evo Epyder 5.2 V10 640 (2.74 s), Mclaren Artura (2.72 s). Each one can be raced against the Ifr Aspid GT-21 Invictus 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 Ifr Aspid GT-21 Invictus is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 10 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.