Identity
Capture the exact current in-game engine and vehicle labels before merging aliases.
Source-scoped rankings for the questions the newest reviewed benchmark can answer, plus explicit Not ranked states where it cannot.
CREATOR-OBSERVED / NOT SITE-TESTEDThe V8 row shows 262 km/h, while Engine-L shows 9.683 seconds from 0–100 km/h. These are Creator-observed, not site-tested values for Buggy, Normal Gearbox, and off-road tyres—not universal engine stats. Long-distance, beginner, and experimental goals remain Not ranked.
Speed and acceleration use same-vehicle creator overlays. Unsupported goals remain Not ranked instead of inheriting older community guesses.
| Scenario | Provisional order | Why these leads | Confidence | Verify next |
|---|---|---|---|---|
| Best for speed |
| Visible creator overlays for Buggy runs in the 2026-08-31 benchmark. Every row uses Normal Gearbox and the creator's default off-road Buggy tyres. | Shown in a dated video | Keep Buggy, Normal Gearbox, off-road tyres, route, direction, load, condition, and build unchanged. |
| Best for acceleration |
| Fastest three 0–100 km/h Buggy overlays in the reviewed extract; Engine-U follows at 10.883 seconds under the same disclosed broad setup. | Shown in a dated video | Repeat the same 0–100 interval with Buggy, Normal Gearbox, off-road tyres, route, input, and server build. |
| Best for long distance |
| The reviewed August 31 benchmark does not publish one controlled fuel- or battery-consumption route for these Buggy pairings. | Not confirmed | Record starting and ending resources, distance, route, vehicle, load, gearbox, tyres, and reserve target. |
| Best beginner setup |
| The August 31 benchmark measures acceleration and top-speed overlays, not acquisition, repair cost, fuel loop, compatibility, or recovery difficulty. | Not confirmed | Confirm acquisition, fit, required resources, start reliability, and recovery cost first. |
| Experimental build |
| A single Electric/SMZ Microcar row exists, but Jet and other experimental setups are not in the August 31 reviewed extract on a shared vehicle. | Not confirmed | Confirm the current entity, vehicle fit, power loop, controls, and one same-route comparison before ranking it. |
Evidence boundary: the ranking transcribes visible overlays from one August 31 creator benchmark. It is not official data, broad player consensus, or a site-run benchmark. Gearbox Pro, other tyres, routes, loads, and newer builds require separate tests.
Capture the exact current in-game engine and vehicle labels before merging aliases.
Confirm the engine produces a usable vehicle state before scoring performance.
Record fuel or battery plus visible oil, cooling, load, and damage conditions.
Keep distance, terrain, direction, build, vehicle, load, and finish rule stable.
State whether the result answers speed, range, acceleration, access, cargo, or experiment fit.
Eleven engine chapters with Normal Gearbox disclosed for every run and default off-road tyres disclosed for Buggy runs.
Download source video ID, timestamp, engine, vehicle, gearbox, tyres, 0–100 time, top-speed overlay, and creator-observed scope.
Explains the eleven dated chapters, disclosed conditions, comparison limits, and alias gaps.
Keeps the 52:25 Buggy overlay attached to Normal Gearbox, off-road tyres, and its creator-observed boundary.
This ranking reads one dated creator benchmark; it is not a promise about every vehicle or the latest server build. Read the Gearbox Balance context before comparing it with an older table or a different gearbox setup.
The V8 row shows the highest visible top-speed overlay at 262 km/h. That belongs to one creator-observed Buggy, Normal Gearbox, off-road tyre setup.
No. It is a provisional source-scoped view of timestamped creator overlays, with unsupported scenarios left Not ranked.
Not ranked here. The August 31 extract does not include one shared, controlled resource-consumption route for the compared Buggy setups.
Record exact labels, vehicle, load, route, direction, server build, resource start and end states, damage, and a repeatable result.
First compare the source date, vehicle, gearbox, tyres and measurement being reported. Differently configured results should remain separate; averaging them would not create a valid current engine statistic.
It created the need for a dated comparison, but the ranking itself is this site's source-scoped reading of one creator benchmark. It is not an official developer tier list.
The archived Electric result uses an SMZ Microcar, while the comparable acceleration order uses Buggy rows. Changing the vehicle prevents an engine-only comparison. Inspect the original setup columns rather than ranking from the time alone.