utc now / zones / kst-to-utc

KST to UTC converter

UTC is 9 hours behind KST right now. Live clocks on both sides, a direct time input, the full 24-hour table with a permalink per hour, and the real daylight-saving state — computed from the IANA tz database on every request, never from a stored offset.

Korea Standard Time · Asia/Seoul
09:26:11
Thursday, 13 August 2026 · KST · UTC+09:00
⇄
Coordinated Universal Time · UTC
00:26:11
Thursday, 13 August 2026 · UTC · UTC+00:00

Convert an exact time type it — no sliders

00:26
swap

Conversion runs in your browser against the same IANA rules the server uses, so it keeps working offline and nothing you type is sent anywhere.

Daylight saving right now

Coordinated Universal Time

UTC is currently on UTC (UTC+00:00).

no clock change scheduled — this zone is fixed at UTC+00:00

UTC is the reference clock every other offset is quoted against. It has no daylight saving and never shifts.

Korea Standard Time

Asia/Seoul is on KST (UTC+09:00).

no clock change scheduled — fixed at UTC+09:00

Korea Standard Time is UTC+9 year-round, identical in offset to JST.

Best time to call green = 09:00–18:00 on both sides

No overlap inside a 09:00–18:00 day on both sides. Someone has to take an early or late slot — the table below shows exactly which hours are least bad.

Google Calendar Outlook download .ics

KST to UTC, hour by hour 13 August 2026 · every row is a permalink

KST UTC 12-hour Day Permalink
00:00 15:00 UTC 3:00 PM previous day 00:00 →
01:00 16:00 UTC 4:00 PM previous day 01:00 →
02:00 17:00 UTC 5:00 PM previous day 02:00 →
03:00 18:00 UTC 6:00 PM previous day 03:00 →
04:00 19:00 UTC 7:00 PM previous day 04:00 →
05:00 20:00 UTC 8:00 PM previous day 05:00 →
06:00 21:00 UTC 9:00 PM previous day 06:00 →
07:00 22:00 UTC 10:00 PM previous day 07:00 →
08:00 23:00 UTC 11:00 PM previous day 08:00 →
09:00 00:00 UTC 12:00 AM same day 09:00 →
10:00 01:00 UTC 1:00 AM same day 10:00 →
11:00 02:00 UTC 2:00 AM same day 11:00 →
12:00 03:00 UTC 3:00 AM same day 12:00 →
13:00 04:00 UTC 4:00 AM same day 13:00 →
14:00 05:00 UTC 5:00 AM same day 14:00 →
15:00 06:00 UTC 6:00 AM same day 15:00 →
16:00 07:00 UTC 7:00 AM same day 16:00 →
17:00 08:00 UTC 8:00 AM same day 17:00 →
18:00 09:00 UTC 9:00 AM same day 18:00 →
19:00 10:00 UTC 10:00 AM same day 19:00 →
20:00 11:00 UTC 11:00 AM same day 20:00 →
21:00 12:00 UTC 12:00 PM same day 21:00 →
22:00 13:00 UTC 1:00 PM same day 22:00 →
23:00 14:00 UTC 2:00 PM same day 23:00 →

Every hour as its own page

00:00 KST 01:00 KST 02:00 KST 03:00 KST 04:00 KST 05:00 KST 06:00 KST 07:00 KST 08:00 KST 09:00 KST 10:00 KST 11:00 KST 12:00 KST 13:00 KST 14:00 KST 15:00 KST 16:00 KST 17:00 KST 18:00 KST 19:00 KST 20:00 KST 21:00 KST 22:00 KST 23:00 KST

KST to UTC — questions

What time is it in UTC when it is KST now?
UTC is currently 00:26 on Thursday, 13 August 2026 (UTC, UTC+00:00), while KST is 09:26 (UTC+09:00). That is 9 hours behind the source clock right now.
How many hours behind is UTC of KST?
9 hours at this moment. The gap is not constant across the year: Korea Standard Time and Coordinated Universal Time change clocks on different dates (or one of them not at all), so a difference you hard-code in summer can be an hour wrong in winter. The table on this page is computed from the current tzdata rules, not from a fixed offset.
Is UTC on daylight saving time right now?
No. UTC is on UTC (UTC+00:00) at the moment.
Does UTC observe daylight saving time?
No. UTC stays on UTC+00:00 all year, so the difference from KST only moves when KST itself changes.
Is there any working-hours overlap between KST and UTC?
Not inside a normal 09:00-18:00 day on both sides — the 9-hour gap is too wide. One party has to take an early or late slot; the hour table above shows exactly which hours land where so you can pick the least painful one.
Which IANA timezone name should I use for UTC in code?
Use UTC. Abbreviations like UTC are ambiguous and not resolvable by most libraries — Python's ZoneInfo, Java's ZoneId, Go's time.LoadLocation and JavaScript's Intl all expect the IANA name. Hard-coding UTC+00:00 instead will be wrong the moment the rules change.

Keyboard shortcuts

cCopy the ISO 8601 timestamp
uCopy the Unix timestamp
/Focus the timezone search
tToggle light and dark
?This help
EscClose