5 min read
Two histories can describe the same round
A Crash history strip usually answers a round-level question: where did this round end? Your own entry record answers a different question: what happened to the entry attached to your account? Keeping those questions separate prevents a common mistake—using the final multiplier to calculate a return that was never accepted for your entry.
SmartSoft lists live player data and round history as features of JetX. That is an example from another product, not confirmation of the screens in Master Crash. Whatever the labels in your installed game, look for a round reference and an entry reference before comparing numbers. If a list shows other players, their accepted exits are not your account record.
Example: the round ends at 3.4×, your exit is 1.6×
Consider a fictional record labelled R-204. It shows an accepted entry of 10 units, a confirmed cash out at 1.6× and a final round multiplier of 3.4×. Under the simple model used in our calculation guide, the total return is 16 units and the net result is +6. The later 3.4× describes the round’s ending; it does not increase an entry already closed at 1.6×.
Now consider a second entry in the same round with no accepted exit. Its outcome cannot be copied from the first entry. In a model where an open entry loses when the round ends, that second 10-unit entry returns 0. These are explanatory units and assumptions, not a Master Crash payout table or a recommendation to choose either multiplier.
- Final round multiplier: 3.4×
- Status: round ended
- Describes the whole round
- Entry: 10 units
- Accepted cash out: 1.6×
- Total return: 16 units; net result: +6
In this example, the later 3.4× does not change the entry already closed at 1.6×. Returned units include the original entry; no fees or other balance changes are assumed.
Read the status before doing arithmetic
A useful record has a game name, round identifier, entry amount, accepted exit if any, total return and final status. Not every interface exposes every field. A blank exit may mean no accepted cash out, but it may also be an incomplete display. Read the legend or rules before treating a blank, dash or zero as a final loss.
Separate “pending” from “settled” and “rejected” from “accepted”. A balance snapshot can include other activity, so a balance difference alone may not identify this round’s return. Start from the entry, then match its result to the account movement. If the necessary link is missing, describe it as missing rather than filling the gap with an estimate.
Match the round, then compare the time
The same displayed time can refer to an entry request, an accepted action or a settled result. Write down the label as well as the clock value. Include the date and time zone, especially if the app and your phone use different settings. A screenshot saying “20:14” is less useful than “13 October, 20:14 IST, result screen”.
Use the round identifier as the main link between screenshots when one is available. Do not assume two nearby rows belong to the same round merely because their times are close. If a screenshot was captured after reconnecting, say so: it may show the latest round rather than the one that was visible when the connection failed.
A short history is not a next-round signal
A run of small multipliers can look like a pattern when placed beside one large result. That appearance does not establish the next outcome. Colour coding, a leaderboard and another player’s exit also describe displayed data, not a promise that the next round will compensate for earlier losses. No multiplier is “due” merely because it has not appeared recently.
The UK Gambling Commission’s RNG standard discusses unpredictability for systems within its remit. It provides background for this distinction; it does not certify Master Crash. A visible sample cannot independently verify a game’s algorithm, payout rate or published fairness claims. A verification tool, where genuinely provided, needs its own documented inputs and method.
Turn a mismatch into a clear question
A useful support question is specific: “For R-204, my entry record says pending, but the round is finished. Please confirm the settled entry status.” Attach the relevant record with private information hidden. Keep the original screenshot for your own files and note when it was taken; avoid editing the numbers you are asking support to check.
If the question concerns a bank withdrawal, use that transaction’s reference separately. A successful round cash out is not proof that a withdrawal has completed. The related support guide explains which identifiers help and which details—passwords, OTPs and payment PINs—must stay out of the report.
Two saved rows can be one updated entry
When collecting screenshots, do not automatically count every visible row as another stake. Imagine saving an entry while it is pending, then saving the same entry after settlement. If the product exposes a stable entry identifier, compare that identifier together with the round reference. Two views of one identifier may show a status change, not two accepted entries. The example below assumes those identifiers are available.
Swipe across to see all columns.
| Saved view | Entry / round | Status |
|---|---|---|
| First capture | E-7 / R-41 | Pending |
| Later capture | E-7 / R-41 | Settled |
Keep both captures as evidence of the change, but use the final record once when reconciling accepted stakes and returns. If the identifiers differ or are missing, do not merge the rows merely because the amounts look identical. The calculation guide assumes a complete list of distinct entries, so resolving duplicates comes before adding the amounts.
Sources and scope
- SmartSoft — JetX product page: round history in a separate game
- UK Gambling Commission — RTS 7: random outcomes (background, not Master Crash certification)
- Crash multiplier calculation
- Prepare a support request
Product-specific controls remain subject to the installed app. Illustrations are explanatory and do not represent measured game results or genuine app screenshots.
