Is it the same round? Match game, ID and time before comparing history
Two records with different dates may refer to the same moment. The round can also be different even if the short ID seen is the same. Read full game identity and time zone before counting or linking entries.
For the topic overview, see Mobile: clear controls and secure access.
You have a screenshot of the slot history and another note from another screen. The first is dated 4 October; the second is 5 October. Before saying they are different rounds, check if one is UTC and the other is UTC+8. The different dates may simply be the result of a time zone change.
There is also the opposite problem: R-041 is written identically, but a different game variant is on one record. We don’t know if the identifier is unique across platforms, just one provider, or one game. So code isolated from its source is not enough.
Select the detail of the round, not just the total movement of the account
“What round is this?” is a different question. and “How much is the total movement in the account?” As an example of this difference, illustrated by UK Gambling Commission RTS 1 the account history which may include deposits, withdrawals, bets, results and winnings; may also contain detailed or summarized gaming information. This is a Great Britain technical reference, not a statement of Philippine law or an operator review.
If only the daily total is visible, that’s not enough to attach to a screenshot of a particular round. Open detail view if available. Record the full game title and variant, provider label, ID, timestamp including time zone, and when the record was taken. “Play time” and “screenshot time” are not automatically the same.
4 October in UTC, 5 October in UTC+8
We will use a fictional game Crystal Cards — Classic and source label that P-A. These are just placeholders for the worksheet, not real providers or products. Both fictitious account views are compared; no personal details in the example.
In the specification of R-041, it is written 4 October 2026, 16:02:30 UTC. When displayed in UTC+8, add eight hours: 5 October 2026, 00:02:30 UTC+8. The date has passed, but the moment has not changed. If the filter is only “4 October” in a view that uses UTC+8, the entry may not be included in that result.
Neither of the two dates need be considered wrong. What is needed is the same basis of comparison. First keep the original timestamp and add a separate normalized time; do not erase the source time zone. If no zone is entered, mark it as unknown instead of assuming the system used phone time.
Five notes, different things can be said
| note | Game and source | ID and recorded event time | Reasonable reading |
|---|---|---|---|
| A: first detail view | P-A · Crystal Cards — Classic | R-041 · 4 Oct 16:02:30 UTC | Base record for comparison; in UTC+8 is 5 Oct 00:02:30 |
| B: different time display | P-A · Crystal Cards — Classic | R-041 · 5 Oct 00:02:30 UTC+8 | Identity fields and normalized time match; can be associated with the same round in the worksheet |
| C: another variant | P-A · Crystal Cards — Turbo | R-041 · 5 Oct 00:02:30 UTC+8 | There is an opposite variant; do not automatically combine with A |
| D: different code | P-A · Crystal Cards — Classic | R-042 · 5 Oct 00:03:00 UTC+8 | Not equal to R-041 because the time is close; separate entry first |
| E: broken screenshot | I don’t see the variant | R-041 · “00:02”; no date or zone | Not enough to match reliably; a complete and sourced record is required |
In A and B, the time is exactly the same after the conversion. In D, the interval is thirty seconds. But that gap is not proof that this is a new paid bet, nor is it a reason to delete it as a duplicate. Documented meaning of ID and transaction type is still needed in the system itself.
A–B match is a result based on our complete fictional inputs. In real history, there may be separate parent rounds, subrounds or transaction identifiers. Follow the labels and the operator’s explanation; don’t create your own merge rule just from code similarity.
Matching identity is not yet confirmed settlement
Assume that both R-041 has been determined. In the first reading, the status is “pending”; in the later detail view, “completed.” That could be the updated status of the same entry, not two different rounds. Time two observations to show the sequence, instead of counting one round for each screenshot.
After aligning the round, use the single-stake tumble ledger to keep component awards separate from running totals.
Pending also does not mean that the award is zero or that the request has failed. Missing status, last seen animation and confirmed result are different things. In UKGC RTS 10, the handling of interruption varies by stage: the result may remain when the gamble has been received and the customer no longer has influence; there is a different handling before generating the outcome, and there is a restoration for a game with many stages. This is also a Great Britain reference. It does not prove which happened to an account.
So no new wager is needed to check an old record. What can help is history detail and the operator’s current interruption policy. If the display is frozen and the request has not been verified, keep the note unresolved until confirmation.
What to keep when it needs to be clarified?
For your own comparison, save the full title and variant, source screen, ID, original timestamp and zone, normalized time, and status at the time of reading. For questions about the account, use the support of the operator of record. game ph guide cannot see your account or settlement.
The description could be as short as this: “R-041, Crystal Cards — Classic, 4 Oct 16:02:30 UTC; same as 5 Oct 00:02:30 UTC+8. Pending on first reading; asking for current confirmed status.” This is a fictitious example of an obvious question, not a real support request sent. No need to include password, OTP or full payment details.
What if only minutes are displayed?
Do not invent an exact second. If the display cannot distinguish two entries, use other verified fields or request more complete details. ‘00:02’ is less precise than ‘00:02:30.’
Can the balance be used to verify ID?
No longer alone. There may be other moves at the same time. This worksheet is for connecting identity and time; it does not reconcile the account balance or calculate the prize.
Naa game format library the hubs for different mechanics. Also read the checklist on game identity and records, or return to game ph homepage and guides. For incorrect links or article explanations, use the online chat.