Asia/Novokuznetsk time zone
9:02PMUTC+7
UTC+7UTC+7+12 h vs New York (you)
No transitions: Asia/Novokuznetsk stays on UTC+7.
About Asia/Novokuznetsk
Asia/Novokuznetsk is the IANA time zone for MSK+04: Kemerovo in Russia. It currently keeps UTC+7 all year.
Its principal location is Novokuznetsk at 53.75° N, 87.12° E.
Rule for future years (POSIX TZ string)
<+07>-7
The standard time is called “+07” (a numeric abbreviation) and is UTC+7. POSIX writes the offset with the opposite sign (west of Greenwich is positive), which is why the string says "-7". There is no daylight saving rule: the zone stays on this offset for every year after the end of its explicit transitions. Software that has no full tzdata copy, such as many embedded devices, can use this string directly as the TZ environment variable.
History of Asia/Novokuznetsk since 1970
The record starts with local mean time (UTC+5:49), which ended on May 1, 1924. The first daylight saving time in the record is in 1981.
| Years | Clocks | Abbreviations |
|---|---|---|
| 1970–1980 | UTC+7 all year | — |
| 1981–1990 | UTC+7 in winter, UTC+8 in summer | — |
| 1991 | UTC+7 until September 29, then UTC+6 | — |
| 1992 | UTC+6 in winter, UTC+8 in summer; also UTC+7 for part of the year | — |
| 1993–2009 | UTC+7 in winter, UTC+8 in summer | — |
| 2010 | UTC+7 until October 31, then UTC+6 | — |
| 2011 | UTC+6 until March 27, then UTC+7 | — |
| 2012 onward | UTC+7 all year | — |
Before 1970
2 offset changes before 1970 in the record:
- Thursday, May 1, 1924: UTC+5:49 → UTC+6
- Saturday, June 21, 1930: UTC+6 → UTC+7
tzdata commits to accuracy from 1970 for every zone (zone1970.tab); earlier entries are historical research and may be incomplete.
Aliases and zones with the same clock
Other zones that keep exactly the same time under the current rules (but have a different history): Antarctica/Davis, Asia/Bangkok, Asia/Barnaul, Asia/Ho_Chi_Minh, Asia/Hovd, Asia/Jakarta, Asia/Krasnoyarsk, Asia/Novosibirsk, Asia/Pontianak, Asia/Tomsk.
Convert Novokuznetsk time
Using Asia/Novokuznetsk in code
Every major platform reads the same IANA ID. Store instants in UTC and convert with the ID at display time; never store a fixed offset for a place that has daylight saving time.
// JavaScript
new Date().toLocaleString('en-US', { timeZone: 'Asia/Novokuznetsk' })
# Python 3.9+
from zoneinfo import ZoneInfo
from datetime import datetime
datetime.now(ZoneInfo('Asia/Novokuznetsk'))
// Java
java.time.ZonedDateTime.now(java.time.ZoneId.of("Asia/Novokuznetsk"))
// Go
loc, _ := time.LoadLocation("Asia/Novokuznetsk")
time.Now().In(loc)
-- PostgreSQL
SELECT now() AT TIME ZONE 'Asia/Novokuznetsk';
# Shell
TZ='Asia/Novokuznetsk' datePlatforms ship their own copy of tzdata and update it on their own schedule. After a rule change, outputs can differ until the platform updates; this page uses tzdata 2026f.