◉The Clock Desk Open the partner account
paid
Affiliate disclosure. The partner link in the masthead and in the band beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. The subject of this desk is the clock an account runs on, so its own interest is stated here rather than left for a footer: one link funds the site, and no operator, game or regulator is named, rated or recommended anywhere on it.
The Clock Desk / The timestamp
The record

The time written on a transaction

A bet, a deposit, a credit and a message each carry a time. That time is written by the operator, on the operator's clock, in a zone that on 40 invented terms pages is stated nowhere, and it is the number every dispute about a moment is actually decided on.

Open the partner accountRead the time clauses
Account spec
Written by
the operator
Written in
unstated on 40 of 40 pages
Readable by you
as a display only
Decides
the side of a cut-off
the boundaryThe instant the account's day is measured from. On the samples it is 00:00 UTC, which is a different wall-clock moment for every reader.
the countdownWhat a window is measured from and whether day one counts. A window advertised as 30 days delivers 29 days 23 hours 59 minutes on the sample.
the calendarThe working-day clock money moves on, with its cut-off, its weekends and its holidays. One working day covered 87 hours 30 minutes on the sample.
Direct answerA transaction's timestamp is written by the operator on the operator's clock, normally in UTC, and it is the authoritative record of when a thing happened. Your device shows a different time, and on sample G none of 40 invented terms pages states which zone the stored record uses, so the number that decides a dispute is one the page does not explain.

Three clocks, one transaction

The same accepted bet, three readingsinstant of acceptance, on the operator's clock 2026-03-07 15:00:00.000 UTC your device, 3.2 s slow 14:59:56.800 local (UTC+0) your local conversion 15:00:00.000 displayed in your zone stored timestamp 2026-03-07 15:00:00 UTC three numbers, one event the first two are displays, the third is the record and only the third is the one a query is answered from

What a stored timestamp can settle

Can settle

Which side of a line

Whether a bet, a claim or a withdrawal request fell before or after a cut-off. The stored time is an instant, and an instant has no side to argue about once the zone is known.

needs
the zone
sample
stated 0 of 40 times
Can settle

The order of two events

Which of two transactions came first. Ordering needs only one clock, so it survives an unstated zone, which is why a record can be internally consistent and still unreadable to a player.

needs
nothing further
usable for
sequence
Cannot settle

The deadline you believed

A stored time cannot tell you what you were shown at the moment you acted. That is a display question, and the display is on your device, not in the operator's record.

lives in
your device
kept by
you
Cannot settle

What the clock should have been

A record shows what the system did, not whether the deadline published to you was the one applied. Where the terms state a zone and the record uses another, the two statements have to be reconciled by asking, not by reading.

needs
the terms' zone
sample
9 of 40 state one

Reading a record in practice

  1. Find the timestamp and its format. An ISO-8601 value ending in Z is UTC by definition, which is more information than the page around it usually gives.
  2. Convert it once, and write the result down. The conversion is the only step that depends on your zone, and once done the instant is fixed.
  3. Compare it with the stated line. If the terms state a cut-off with a zone, the comparison is arithmetic. If they state no zone, the comparison is an assumption and should be named as one.
  4. Keep the record before the display. A screenshot of your own device shows your clock; the transaction record shows the operator's. Where they disagree, the operator's is the one the rules were applied on.
Not an argument about fairness. Nothing here suggests a stored time is wrong. The point is narrower and more useful: an instant without a stated zone cannot be checked by the person it governs, which is why this desk puts zones in every sentence it writes.
Whose midnightthe three zones in play The instant a market closesthe line and the devices What an hour of play measuresunits against minutes Every figure in one placewith the arithmetic behind it