GTA 6 comes out on 19 November 2026. That sentence hides fifteen different moments.
Console games unlock at midnight, but whose midnight? Rockstar's support page answers it: the game unlocks at midnight in the time zone of the store your account belongs to, region by region. New Zealand goes first. Mexico goes last, nineteen hours later. A player in Los Angeles on a US account gets it at 9 pm on the 18th, because the US store follows New York's midnight.
I built Route Six, a small fan site that tells you your exact minute. Here is how the time maths works, because it is a nice little problem and most of it is plain Intl.
Store a moment, never a clock time
The first trap is writing "midnight" anywhere in code. Midnight is not a moment, it is a label that each time zone puts on a different moment. So the data file stores each store region's unlock as one UTC instant:
{ "id": "us", "name": "United States, Canada", "utc": "2026-11-19T05:00:00Z",
"zones": ["America/New_York", "America/Chicago", "America/Phoenix", "America/Los_Angeles", "America/Kentucky/*", "…"] }
{ "id": "uk", "name": "United Kingdom, Ireland, Portugal, Iceland", "utc": "2026-11-19T00:00:00Z",
"zones": ["Europe/London", "Europe/Dublin", "Europe/Lisbon", "Atlantic/Reykjavik", "…"] }
{ "id": "in", "name": "India", "utc": "2026-11-18T18:30:00Z",
"zones": ["Asia/Kolkata", "Asia/Calcutta"] }
Fifteen rows like that cover every store (the zone lists are shortened here). The instant is the fact; every clock on the page is just that instant printed in some time zone.
Which store are you?
The browser knows its IANA zone:
const zone = Intl.DateTimeFormat().resolvedOptions().timeZone; // "Asia/Karachi"
Each region lists the zones it covers, with a * for families like Australia/*:
function zoneMatches(pattern: string, zone: string): boolean {
return pattern.endsWith('*') ? zone.startsWith(pattern.slice(0, -1)) : pattern === zone;
}
export function detectRegion(): string {
const zone = Intl.DateTimeFormat().resolvedOptions().timeZone;
const hit = regions.find((r) => r.zones.some((z) => zoneMatches(z, zone)));
return hit ? hit.id : 'local';
}
It is only a first guess. Your store is where the account was made, not where you sit. Pakistan has no PlayStation Store at all, so people there use UAE, Saudi, UK or US accounts, and the answer runs from 1 am to 10 am on the 19th depending on which one. The page shows the guess and a picker, and the Pakistan page lists all four.
Printing the clock in someone else's zone
Intl.DateTimeFormat takes a timeZone option, so printing the US unlock on a Los Angeles clock needs no library:
function clock(date: Date, timeZone?: string): string {
const p: Record<string, string> = {};
for (const part of new Intl.DateTimeFormat('en-GB', {
hour: 'numeric', minute: '2-digit', hourCycle: 'h12', timeZone,
}).formatToParts(date)) p[part.type] = part.value;
return `${p.hour}:${p.minute} ${p.dayPeriod.toLowerCase()}`;
}
clock(new Date('2026-11-19T05:00:00Z'), 'America/Los_Angeles'); // "9:00 pm"
clock(new Date('2026-11-19T05:00:00Z'), 'America/Phoenix'); // "10:00 pm"
formatToParts is the useful bit: you get the hour, minute and day period as separate pieces and can lay them out however the design wants, instead of parsing a formatted string.
Arizona is the case that catches people. It ignores daylight saving, so in November it sits on the same clock as Denver, and the zone database handles that for you as long as you never do the offset arithmetic by hand.
Half-hour zones
India is UTC+5:30, so the Indian store unlocks at 18:30 UTC. Adelaide is +10:30 in November, Darwin +9:30, Newfoundland −3:30. Anything that rounds offsets to whole hours gets these wrong. Keeping UTC instants in the data and letting Intl print them means the half-hours come out right without a single special case.
The countdown and React
The live countdown re-renders every second. The page is built ahead of time and has no idea what time zone the reader is in, so the HTML ships dashes in the countdown and the browser fills in the numbers and "your" clock once it is running. Printing the reader's local time at build time would bake in the build machine's zone and then fail to hydrate for everyone else.
Static, on purpose
The whole site is a Next.js static export (output: 'export') served from Cloudflare's static assets: 23 pages, one per country plus the tools, and a small Worker that counts page views. Every page is generated from the same data file, and a build fails if a page cites a source that does not exist in that file.
If you are on a console, the unlock time page shows your minute. If you are a developer, the takeaway is the boring one: store instants, print with Intl, and never write the word midnight in a variable name.
Disclosure: I make Route Six. It is an unofficial fan site, not affiliated with Rockstar Games or Take-Two Interactive.
Top comments (1)
Midnight can also just not exist. Where the clocks jump forward at midnight, that day starts at 01:00.
I counted a habit's tracking days from local midnights, so on that day today fell out of the count for anyone in those zones. Counting calendar dates instead of midnights fixed it.