The Clock Desk / Overview

Desk 66 · time and the account

The clock a gambling account runs on

An account has a balance, a licence and a limit, and it also has a clock. This desk is about that clock: which day the account keeps, whose midnight a reset follows, what a countdown on a credit is measured from, the instant a market stops taking bets, the notice on a maintenance window, the zone a stored timestamp is written in, and the calendar money moves on.

Open the partner account Read the time clauses

Account spec

Operator day: 00:00 UTC
Reader in UTC+13: 13:00 local
The same reset costs: 14 h 20 m or 2 h 00 m
Pages stating a zone: 9 of 40

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.

Two marks on one ring. The green hand points at the reader's own midnight. The rust hand points at 13:00 local, which is the instant the operator's 00:00 UTC boundary falls on that reader's clock. One day, two boundaries, thirteen hours apart: everything else on this desk follows from that pair of marks.

00:00 localone local day for a reader in UTC+1324:00 local

the account day still running (00:00-12:00 local) the last hour before the boundary (12:00-13:00) the account day that opens at the reset (13:00-24:00)

One track, three clocks. The reader's day runs 00:00 to 24:00 local. The operator's day runs 00:00 to 00:00 UTC, which on this reader's clock is 13:00 to 13:00, so two thirds of the reader's morning belongs to an account day that opened yesterday. A credit that expires "at the end of the day" dies in the hour before the reset, which is 12:00 local here and has nothing to do with this reader's midnight.

Direct answerA gambling account does not run on your clock. It runs on the operator's, which is usually UTC, and it is the operator's clock that decides when a daily limit resets, when an offer opens, when a bonus expires and when a working day starts. The same 200.00 daily loss limit leaves one reader waiting 14 hours 20 minutes for the reset and another 2 hours, purely because of where they are.

Nothing here is about whether a number is fair. It is about which moment a number refers to. Four questions cover most of it, and each has a page: which day the account is keeping, what resets and on which clock, what a countdown is measured from, and the instant a thing closes. Around them sit the zone itself, the working-day calendar that money moves on, the clock a live round runs on, and the timestamp a dispute turns on.

Why the clock is the subject rather than a detail

Every mechanic a player meets in a gambling account has a time property, and almost none of them is published in a form the player can act on. A limit "resets daily" and does not say on whose day. A bonus "expires in 30 days" and does not say whether the day it is credited counts. A withdrawal "takes one working day" and does not say which calendar that is. A market "closes at kick-off" and the kick-off in the reader's own time zone is a different clock from the one the market closes on.

The desk's rule follows from that: no time on this site is quoted without its zone and its offset. Where a source states a time without one, that absence is the finding and it is reported as one.

Sample A - the same instant, three wall clocksoperator reset 00:00 UTC reader in UTC+13 00:00 + 13 h = 13:00 the same calendar day reader in UTC+0 00:00 + 0 h = 00:00 the same calendar day reader in UTC-8 00:00 - 8 h = 16:00 the previous calendar day wall-clock spread between the three readers 13:00 - (16:00 - 24 h) = 13:00 - (-8:00) = 21 h plus the day label, which differs for one reader of the three

The eight samples this desk is built on

Every figure on the site derives from eight invented samples, defined here once. Each is labelled illustrative, none is quoted from a company, and the arithmetic behind each is shown on the numbers page so it can be re-derived rather than believed.

Sample A

The zone

One operator publishes 00:00 UTC for its daily reset; three readers sit at UTC+13, UTC+0 and UTC-8. The reset is one instant and three different wall-clock moments.

spread: 21 h of wall clock
day label: differs for 1 of 3

Sample B

The reset

A 200.00 daily loss limit is hit at 09:40 UTC by the UTC+13 reader and at 22:00 UTC by the UTC-8 reader. The reset lands at 00:00 UTC for both.

UTC+13 waits: 14 h 20 m
UTC-8 waits: 2 h 00 m

Sample C

The countdown

A credit at 00:00 UTC on 1 March expires on the 30th day at 23:59:59 UTC. The window is advertised as 30 days.

actual window: 29 d 23 h 59 m
lost at the start: 1 s of day one

Sample D

The cut-off

A market closes at 15:00:00.000 UTC. Two bets are placed sixty milliseconds either side of it, from two devices whose clocks disagree with the server.

accepted: 14:59:59.940
rejected: 15:00:00.060

Sample E

The working day

A withdrawal is requested on Friday at 17:30 local against a 16:00 UTC cut-off, with the following Monday a public holiday.

operator's view: 1 working day
elapsed: 87 h 30 m

Sample F

The round

A live table runs a 12-second bet window, a 3-second no-more-bets pause and a 25-second deal and settlement.

per round: 40 s
rounds an hour: 90

Sample G

The book

Forty invented terms pages are read for how they describe time: the zone, the counting convention, the cut-off and the word used for "later".

state a zone: 9 of 40
state the counting: 2 of 40

Sample H

The hour that moves

A daily allowance fixed at 00:00 UTC crosses a daylight-saving change in the reader's own zone.

elapsed: 24 h 00 m
wall clock reads: 25 h or 23 h

The one figure to carry away

Sample C - a 30-day countdown, counted inclusivelycredited 1 March 00:00:00 UTC expiry stated the 30th day at 23:59:59 UTC = 30 March 23:59:59 UTC day 1 is 1 March, so the 30 days are 1 March through 30 March elapsed 30 March 23:59:59 - 1 March 00:00:00 = 29 d 23 h 59 m 59 s advertised 30 d = 720 h 00 m 00 s delivered 29 d 23 h 59 m 59 s = 719 h 59 m 59 s shortfall 1 s, because the counting is inclusive local deadline, UTC+13 31 March 12:59:59 local deadline, UTC+0 30 March 23:59:59 local deadline, UTC-8 30 March 15:59:59

A one-second shortfall is nothing. The useful part of the same calculation is the last three lines: the deadline is one instant that falls on two different calendar dates and at three different clock times in the three readers' own terms, so a deadline quoted as a date is ambiguous while the same deadline quoted with a zone is not.

Sample A - one operator, one reset time, three readers
Reader	Offset	00:00 UTC is	Their account day
Auckland	UTC+13	13:00 the same day	13:00 to 13:00
London	UTC+0	00:00 the same day	00:00 to 00:00
Los Angeles	UTC-8	16:00 the day before	16:00 to 16:00
Same instant, three wall clocks	-	spread 29 hours	one day, three boundaries

What this desk is not. It does not tell you when to play, it does not compare operators, and it recommends nothing. Every time figure is illustrative. Where a real mechanism is described — a reset, a cut-off, a working-day calendar — the description is of the mechanism, not of any named operator, and the record of how it is published comes from the 40 invented pages of sample G rather than from a real site.

Where to go next

Which day the account keepsthe operator day, the calendar day and the local day What resets and whenlimits, allowances and offers on one clock What a countdown is measured fromthe credit moment and inclusive counting The instant a market closessixty milliseconds either side of the line Whose midnightUTC, the operator and daylight saving The calendar money moves onworking days, cut-offs and holidays