No current first-party RUNAWAYS loot-price table was found, so the reliable way to compare loot is to read the pawn transaction in the live build. Record the object, visible return, source location, server date, and carrying difficulty. Current walkthroughs mention trophies, rings, jewelry, laptops, toasters, radios, televisions, and other household objects, but those examples do not establish permanent prices.
Items worth testing first
Compact jewelry and trophy-like objects are useful candidates because current community routes identify them and they are easier to carry through doors. Electronics such as laptops and radios are also repeatedly mentioned. Larger objects such as televisions or household appliances may be manageable with a vehicle and clear route, but size can add friction.
These are test groups, not value tiers. Start with one named object that can be identified consistently. Complete a sale, capture the before-and-after balance or transaction message, and repeat. If the model or label differs, keep it as a separate entry rather than averaging unrelated objects.
Measure effective value
Pawn return is only one column. Also record how long the object takes to reach the vehicle, whether it consumes an inventory slot or must be dragged, whether it clears the target’s doorway, and how much police exposure the route creates. A smaller return delivered three times can outperform a larger item abandoned once.
Use the same pawn location for a clean comparison. Route changes introduce fuel and time differences. If a class, backpack, gamepass, or teammate changes carrying behavior, record that separately. The goal is not a universal spreadsheet; it is a decision you can reproduce in the current beta.
A practical comparison format
Test a pawn return cleanly
Begin with a known balance and an empty or documented inventory. Take one object, avoid mixing transactions, and bring it to the same current shop. Save the visible result and the exact date. Repeat once in a fresh server if the number will influence a major purchase or guide claim.
If the shop accepts multiple objects at once, separate the test on another run. If the value changes, check item variant, location, server age, and whether a class or event was active. Do not fill the difference with an assumed bonus.
Choose loot for the route
For a short farm loop, prioritize objects that produce repeatable sales with minimal travel. For a vault attempt, preserve room for vault contents before entering. For a Mexico run, decide whether carrying extra loot is worth the fuel, police attention, and interaction time. The border objective does not require a maximum haul.
Solo players should value door clearance and predictable handling. Crews can assign a driver and carriers, but each extra object still needs a shop interaction and safe departure. Agree on which objects have priority before police pressure makes the choice.
Recognize stale or weak value claims
A screenshot of a number without the item, a list with no check date, and a copied table that never shows a transaction are weak evidence. Search crawl dates are not game test dates. A beta update timestamp also does not prove which price changed.
Use the Updates page as a signal to retest, not as a balance log. If the creator publishes an official table later, compare it with live results and date both. Until then, honest “verify at pawn counter” cells are safer than precise but unsupported amounts.
Sources and confidence
Robbing and pawning is Official. The listed example objects are Community reported or corroborated by current guides. Every exact ordinary loot value remains Needs in-game testing because no first-party current table was verified.