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

Fiat Marea Weekend 2.4 JTD 136

The Fiat Marea Weekend 2.4 JTD 136 reaches 60 mph in 9.35 s (100 km/h in 9.90 s) and covers a standing quarter mile in 17.01 s, tripping the lights at 80.9 mph. It clears the first 60 ft in 2.70 s and the eighth mile in 10.94 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.

Fiat Marea Weekend 2.4 JTD 136 Nissan Sentra 1.8 130

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 Fiat Marea Weekend 2.4 JTD 136
0–60 mph9.35 s
0–100 km/h9.90 s
0–100 mph—
60 ft2.70 s
1/8 mile10.94 s
1/4 mile17.01 s
Trap speed80.9 mph

About the Marea Weekend 2.4 JTD 136

The 1996 Fiat Marea Weekend 2.4 JTD 136 is a front-drive turbodiesel saloon of 1,315 kg with 134 bhp, which works out at 102 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.70 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,014th quickest to 60 mph, and the 102nd quickest of the 455 Fiats here. Its 80.9 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 Fiat Marea Weekend 2.4 JTD 136
Year1996
Power134 hp (100 kW)
Kerb mass1,315 kg
Power to weight102 bhp/t
DrivetrainFront drive
Gears5
EngineTurbodiesel
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Nissan Sentra 1.8 13020129.37 s17.00 s81.6 mph129 bhp
Kia Optima / Magentis 2.0 16V 14420069.30 s17.04 s83.9 mph142 bhp
Kia Rio Sedan 1.6 16V 11020059.29 s17.09 s82.4 mph109 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 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Fiat 0-60 timesevery modelFastest saloon cars3,808 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 Fiat Marea Weekend 2.4 JTD 136 0-60 time?
The Fiat Marea Weekend 2.4 JTD 136 reaches 60 mph in 9.35 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,014th quickest of the 14,946 cars in the set.
What is the Fiat Marea Weekend 2.4 JTD 136 quarter mile time?
17.01 s at 80.9 mph. It reaches the eighth mile in 10.94 s and clears the first 60 ft in 2.70 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Fiat Marea Weekend 2.4 JTD 136 have?
134 bhp and 1,315 kg, which is 102 bhp per tonne. It is front-drive, turbodiesel, with 5 gears and a quoted top speed of 195 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Fiat Marea Weekend 2.4 JTD 136?
Closest here on pace: Nissan Sentra 1.8 130 (9.37 s), Kia Optima / Magentis 2.0 16V 144 (9.30 s), Kia Rio Sedan 1.6 16V 110 (9.29 s). Each one can be raced against the Fiat Marea Weekend 2.4 JTD 136 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 Fiat Marea Weekend 2.4 JTD 136 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.