Identity
Capture the exact current in-game engine and vehicle labels before merging aliases.
Scenario rankings that answer the search directly while keeping source quality visible. Community-reported candidates are starting points for your current build—not hidden official stats.
COMMUNITY-REPORTED / NOT SITE-TESTEDFor acceleration, start with Electric, Jet, and Engine-L. For a beginner setup, inspect Injection, VAZ, and SMZ first. These are Community-reported, not site-tested rankings; compatibility and current-client identity come before the order.
The source data is partly pre-update and not measured on one shared basis. No row is a definitive all-build order.
| Scenario | Provisional order | Why these leads | Confidence | Verify next |
|---|---|---|---|---|
| Best for speed |
| These are the leading speed candidates in the checked secondary community comparison. | Low–medium | Same vehicle, flat route, direction, load, condition, build, and finish point. |
| Best for long distance |
| SMZ is the first efficiency lead; V8 is a reported speed-versus-range tradeoff; Injection is a practical comparison baseline. | Low | Record starting and ending resource state over the same route and reserve target. |
| Best for acceleration |
| Community material places these among acceleration-oriented candidates, but setup and fit can change the result. | Low | Use one vehicle, load, start point, finish marker, input method, and server build. |
| Best beginner setup |
| These are practical first-check leads where availability, compatibility, and an understandable resource loop matter more than peak output. | Low | Confirm acquisition, fit, required resources, start reliability, and recovery cost first. |
| Experimental build |
| These are experimentation leads rather than safe universal recommendations. | Very low | Confirm the entity exists in the current client before planning compatibility or performance tests. |
Evidence boundary: the ranking mainly reflects one secondary community comparison, not official data, broad player consensus, or a site-run benchmark. Only part of the cited consumption data was remeasured after the update.
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.
Names 13 leads and discloses partial post-update measurement coverage. It relies mostly on one tester and community material, so it is neither official nor consensus.
Preserves the 13 community-named leads, alias conflicts, and a controlled comparison method without copying unsupported exact stats.
Separates the speed lead from unresolved compatibility, acquisition, resource, and current-build performance fields.
V8 is the first community-reported speed candidate, while SMZ leads the long-distance shortlist. Neither is an official or site-tested universal winner.
No. It is a provisional scenario ranking built from a disclosed secondary community comparison and creator topic leads.
The shared evidence is partly pre-update and not measured on one common basis, so copying exact figures would imply more comparability than the sources support.
Record exact labels, vehicle, load, route, direction, server build, resource start and end states, damage, and a repeatable result.