A defensible RUNAWAYS class tier list cannot assign S, A, or B ranks yet because the official records checked August 21, 2026 expose class names but no perks. Contractor, Gang Member, Smuggler, Brawler, Scout, Old Ceo, Juggernaut, Breacher, Medic, and Hitman are confirmed identities. Their live effects and unlocks need observation before a ranking can help players.
Why name-based tiers fail
It is tempting to place Juggernaut in a survival tier, Scout in a speed tier, or Medic in support based on ordinary word meanings. That would be inference, not RUNAWAYS evidence. The class might have a different effect, multiple effects, or no current public availability. Product sale status cannot answer those questions.
Community video titles call some classes “best,” but a title lacks the selected loadout, route, build date, perk wording, and controlled comparison. Watch demonstrations to find tests worth repeating, not to import a permanent rank.
Rank by one objective
Choose one task: complete a short robbery, move a known object, breach the same vault, drive the same state segment, recover from the same pursuit situation, or support the same crew. Keep vehicle, fuel, inventory, target, and teammates constant. Change only the class.
Record the exact live class description before starting. Then record a visible outcome such as time, capacity, damage survived, recovery success, or interaction result only if the game exposes it reliably. Repeat at least once in a fresh server before moving the class.
Use route-specific bands
The current public-evidence list remains Unranked. A player with live access can apply these bands separately to robbery, vault, pursuit, and crew support instead of forcing one global order.
Test solo value
Use an ordinary route you already know. Start with the same inventory and vehicle, take the same type of object, and use the same pawn location. Record whether the class changes a visible limitation. Do not count better driving on the second attempt as a class effect.
For Mexico, keep the state route and fuel stops constant. A completion difference across one run is not enough because police, collisions, and server performance vary. Repeat and state the build date.
Test crew value
Assign driver, carrier, tool user, and route caller before selecting classes. Change one crew member’s class and keep the others stable. If the live perk supports a team action, measure that action directly. Avoid declaring a class weak merely because its benefit is not designed for solo play.
Communication can outweigh a minor perk. Keep the route plan and departure signal consistent so the class comparison is not really a coordination comparison.
Update the ranking honestly
When a live description or creator note appears, preserve the exact wording, date it, and test the effect. An API universe timestamp is only a retest signal; it is not proof of a buff or nerf. If the effect changes, retire the old band rather than mixing results.
The absence of a current rank is useful: it prevents players from spending currency or planning a crew around fabricated perks. The Class List remains the canonical identity reference.
Sources and confidence
Class identities and off-sale states are Official. Community tier videos are Discovery leads only. Perks and final rankings are Needs in-game testing, so no letter-tier claims are presented as fact.
A current ranking should always name its objective and build date. A class that helps one crew action may be neutral on a solo pawn loop, and a beta balance change can invalidate both observations without changing the official identity.