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

Hyundai Terracan 3.5i V6 194

The Hyundai Terracan 3.5i V6 194 reaches 60 mph in 9.78 s (100 km/h in 10.32 s) and covers a standing quarter mile in 17.72 s, tripping the lights at 82.0 mph. It clears the first 60 ft in 3.14 s and the eighth mile in 11.69 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.

Hyundai Terracan 3.5i V6 194 Mazda Tribute 2.3 154

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 Hyundai Terracan 3.5i V6 194
0–60 mph9.78 s
0–100 km/h10.32 s
0–100 mph—
60 ft3.14 s
1/8 mile11.69 s
1/4 mile17.72 s
Trap speed82.0 mph

About the Terracan 3.5i V6 194

The 2001 Hyundai Terracan 3.5i V6 194 is an all-wheel-drive naturally aspirated SUV of 1,982 kg with 192 bhp, which works out at 97 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 3.14 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 9,744th quickest to 60 mph, and the 123rd quickest of the 295 Hyundais here. Its 82.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 2 of 2 published acceleration figures for this car.

On paper

Specification Hyundai Terracan 3.5i V6 194
Year2001
Power192 hp (143 kW)
Kerb mass1,982 kg
Power to weight97 bhp/t
DrivetrainAll-wheel drive
Gears4
EngineNaturally aspirated
Top speed111 mph (178 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mazda Tribute 2.3 15420079.77 s17.72 s81.6 mph153 bhp
Pontiac Montana 3.4 V6 18620009.84 s17.79 s80.8 mph184 bhp
Daihatsu Materia 1.5 10320079.81 s17.56 s79.2 mph102 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
Hyundai 0-60 timesevery modelFastest SUVs2,049 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 Hyundai Terracan 3.5i V6 194 0-60 time?
The Hyundai Terracan 3.5i V6 194 reaches 60 mph in 9.78 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,744th quickest of the 14,946 cars in the set.
What is the Hyundai Terracan 3.5i V6 194 quarter mile time?
17.72 s at 82.0 mph. It reaches the eighth mile in 11.69 s and clears the first 60 ft in 3.14 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Hyundai Terracan 3.5i V6 194 have?
192 bhp and 1,982 kg, which is 97 bhp per tonne. It is all-wheel-drive, naturally aspirated, with 4 gears and a quoted top speed of 178 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Hyundai Terracan 3.5i V6 194?
Closest here on pace: Mazda Tribute 2.3 154 (9.77 s), Pontiac Montana 3.4 V6 186 (9.84 s), Daihatsu Materia 1.5 103 (9.81 s). Each one can be raced against the Hyundai Terracan 3.5i V6 194 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 Hyundai Terracan 3.5i V6 194 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.