TL;DR: a round ID identifies an event
Save it with stake, target, accepted cash out, timestamp and transaction entry. It does not predict results.
Where to find it
The identifier may appear in game history, fairness details, account transactions or support exports depending on the version.
Why it matters
Time and multiplier alone may match several events. An ID helps connect game records with account settlement.
Fairness checks
Use values from the same completed round. Mixing IDs, seeds or hashes invalidates the comparison.
Support case file
Include operator domain, account ID, round ID, timestamp, currency, amount and requested resolution. Redact credentials.
Build a complete evidence record
Write down the operator domain, account reference, currency, accepted stake, selected cash-out instruction, recorded endpoint and transaction status. Add the device time and time zone. A complete record lets support locate the event without guessing which visually similar round is being discussed.
Reconcile history with transactions
First match the round identifier in game history. Then compare the corresponding entry in the account ledger. A screenshot of the aircraft or multiplier alone does not establish when the server accepted an instruction, so keep the original history and transaction records whenever possible.
Avoid mixing verification inputs
A fairness check only makes sense when every identifier, seed, hash and result belongs to the same completed round and follows the documented format. Copying one value from another event can produce a failed comparison without showing that the original settlement was wrong.
Share records safely
Send evidence only through the verified operator support route. Redact passwords, one-time codes, full card details and unrelated balances. Preserve an unedited private copy, note the case number and ask for a written explanation that cites the applicable game or settlement rule.
What a round ID cannot prove
The identifier locates a record; it does not by itself prove when a button press reached the server, whether a payout was due or whether a future result is knowable. Interpret it together with the applicable rules, transaction entries and the operator's written response.
A concise support request
State the identifier and discrepancy in the first lines, attach only relevant records and ask which rule controlled settlement. Avoid accusations or multiple unrelated issues in one ticket. A focused request is easier to investigate and creates a clearer escalation record for both the first review and any later formal complaint.
FAQ
What is a round ID?+
An identifier for a specific round record.
Does it predict results?+
No.