The time zone database behind every answer here
Every offset, abbreviation and clock-change date on this site is computed from one pinned release of the IANA time zone database. This page names it, dates it, and says what it cannot answer.
Which release do these times come from?
One release, pinned and committed, rather than whatever version the server or the browser happens to carry. The archive below was downloaded, verified against its checksum and compiled with the reference tooling; the times you read are computed from the result.
Release
2026c
Inspect the release receipt
- 2026c
e0b4b7044b66fbc27bc21d13d18063abcdf78ab58d5ba5fd64bd1a88d86e9d495f45add4d8e65bb6c40249f9c94ca29b72c8ebba8d0e4c468f2965ac77932ef0- 2024–2032
Why not read the time zone data your browser already has?
Because every browser and every server carries its own copy, the copies fall behind the source independently, and no browser interface reports which version it holds. A tool built on that data cannot tell you when it is out of date. Computing from a release named on this page is what makes the opposite possible: this site can say that your device disagrees with it, and which release introduced the difference.
Where do the place names come from?
Place names, their translations and the zone each place belongs to come from a curated extract of GeoNames, downloaded once and committed rather than fetched at build time. GeoNames publishes a rolling daily export with no version tags and no checksums, so the download date and the file hashes below are the whole of the provenance the source makes possible.
Inspect the place-data receipt
- CC-BY-4.0
- Place names and time zones from GeoNames (https://www.geonames.org), CC BY 4.0.
Something here is wrong. What now?
Report it and it gets fixed in the open. Corrections to a rate, a date or a rule are made in the same change that updates the pinned release, and this page's date moves with them.