A matching Tokyo clock does not combine the participants
Seoul and Tokyo both use UTC+09:00 on these 2026 dates, but Seoul retains Asia/Seoul. Two rows can share a clock and still have different availability, titles, or responsibilities. Treat the local-time match as a comparison result rather than collapsing the two people into one schedule.
A dated view of the local clock
| UTC date | UTC offset | Abbreviation | Local date and time |
|---|---|---|---|
| 2026-01-15 | UTC+09:00 | KST | Thu, 15 Jan 2026 · 22:00 |
| 2026-07-15 | UTC+09:00 | KST | Wed, 15 Jul 2026 · 22:00 |
| 2026-10-27 | UTC+09:00 | KST | Tue, 27 Oct 2026 · 22:00 |
| 2026-11-03 | UTC+09:00 | KST | Tue, 3 Nov 2026 · 22:00 |
The European morning reaches the evening here
At 09:00 Berlin on 27 October 2026, Seoul reads 17:00. That is the end of an illustrative working day, not a fifteen-minute shared window. In July, Berlin’s sampled offset moves the same local start to 16:00 Seoul. Check a recurring plan across both seasons.
Build a plan for this city
Select Seoul, add the other participants, and enter the actual meeting date. The planner uses Asia/Seoul; the abbreviation in the table is a display label. Adjust working days, hours, and meeting length before choosing a shared window. The supported planning range is 2026–2035.