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

Nissan Sunny 3dr 1.6 16V 102

The Nissan Sunny 3dr 1.6 16V 102 reaches 60 mph in 9.74 s (100 km/h in 10.31 s) and covers a standing quarter mile in 17.45 s, tripping the lights at 80.3 mph. It clears the first 60 ft in 2.91 s and the eighth mile in 11.30 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.

Nissan Sunny 3dr 1.6 16V 102 Mazda 3/Axela Hatchback 2.0 Skyactiv-G 122

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 Nissan Sunny 3dr 1.6 16V 102
0–60 mph9.74 s
0–100 km/h10.31 s
0–100 mph—
60 ft2.91 s
1/8 mile11.30 s
1/4 mile17.45 s
Trap speed80.3 mph

About the Sunny 3dr 1.6 16V 102

The 1993 Nissan Sunny 3dr 1.6 16V 102 is a front-drive naturally aspirated car of 1,030 kg with 101 bhp, which works out at 98 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.91 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 9,688th quickest to 60 mph, and the 111th quickest of the 263 Nissans here. Its 80.3 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 2 of 2 published acceleration figures for this car.

On paper

Specification Nissan Sunny 3dr 1.6 16V 102
Year1993
Power101 hp (75 kW)
Kerb mass1,030 kg
Power to weight98 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mazda 3/Axela Hatchback 2.0 Skyactiv-G 12220199.74 s17.36 s80.3 mph121 bhp
Honda Civic 1.0 VTEC Turbo (FK)20179.82 s17.45 s79.9 mph127 bhp
Smart forfour 1.3 9420039.83 s17.51 s80.1 mph94 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 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Nissan 0-60 timesevery modelFastest small cars1,681 carsFastest cars of the 1990s2,649 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 Nissan Sunny 3dr 1.6 16V 102 0-60 time?
The Nissan Sunny 3dr 1.6 16V 102 reaches 60 mph in 9.74 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,688th quickest of the 14,946 cars in the set.
What is the Nissan Sunny 3dr 1.6 16V 102 quarter mile time?
17.45 s at 80.3 mph. It reaches the eighth mile in 11.30 s and clears the first 60 ft in 2.91 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Nissan Sunny 3dr 1.6 16V 102 have?
101 bhp and 1,030 kg, which is 98 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Nissan Sunny 3dr 1.6 16V 102?
Closest here on pace: Mazda 3/Axela Hatchback 2.0 Skyactiv-G 122 (9.74 s), Honda Civic 1.0 VTEC Turbo (FK) (9.82 s), Smart forfour 1.3 94 (9.83 s). Each one can be raced against the Nissan Sunny 3dr 1.6 16V 102 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 Nissan Sunny 3dr 1.6 16V 102 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.