New York to Seoul Meeting Times After DST: 2026
On November 2, 2026, 9:00 AM in New York is 11:00 PM in Seoul, on the same date. If Seoul's slot must stay at 10:00 PM, confirm an 8:00 AM New York start instead.
The choice is which city's local time stays fixed. Settle that with the organizer before changing a recurring invitation.
Key Takeaways
- Seoul is 14 hours ahead of New York after the November 1, 2026 clock change. The October examples below have a 13-hour gap.
- Keeping 9:00 AM in New York moves the Seoul occurrence from 10:00 PM to 11:00 PM.
- Keeping 10:00 PM in Seoul moves the New York occurrence from 9:00 AM to 8:00 AM.
- Confirm the next occurrence's date, both local times and its UTC time with the organizer.
What is the New York to Seoul time difference after November 1, 2026?
New York is 14 hours behind Seoul after the November 1, 2026 clock change, so a 9:00 AM New York meeting starts at 11:00 PM in Seoul on the same date. NIST's 2026 daylight saving rules give November 1 at 2:00 AM local time as the end of daylight saving time. The clock moves back to 1:00 AM.
The examples here use America/New_York and Asia/Seoul. In the October rows, their UTC offsets are −04:00 and +09:00. In the November rows, they are −05:00 and +09:00. Subtracting the offsets gives gaps of 13 and 14 hours.
UTC (Coordinated Universal Time) is a shared reference time standard. Comparing both local times with UTC helps confirm that they refer to the same moment.
These city names matter. Use the actual city and meeting date when checking another location; a general US time label is too broad.
Which city's clock should stay fixed in a recurring meeting?
The team has to choose whether New York's hour or Seoul's hour stays fixed, because keeping 9:00 AM in New York moves the Seoul occurrence from 10:00 PM to 11:00 PM. All four dates are Mondays, and both cities have the same date in this example.
On a phone, swipe sideways to read the tables and the full confirmation card.
| Meeting date | New York start | Seoul time |
|---|---|---|
| October 19, 2026 | 9:00 AM, UTC−04:00 | 10:00 PM |
| October 26, 2026 | 9:00 AM, UTC−04:00 | 10:00 PM |
| November 2, 2026 | 9:00 AM, UTC−05:00 | 11:00 PM |
| November 9, 2026 | 9:00 AM, UTC−05:00 | 11:00 PM |
Now keep the Seoul start fixed at 10:00 PM. The change falls on the New York side instead.
| Meeting date | Seoul start | New York time |
|---|---|---|
| October 19, 2026 | 10:00 PM, UTC+09:00 | 9:00 AM |
| October 26, 2026 | 10:00 PM, UTC+09:00 | 9:00 AM |
| November 2, 2026 | 10:00 PM, UTC+09:00 | 8:00 AM |
| November 9, 2026 | 10:00 PM, UTC+09:00 | 8:00 AM |
Those are two different scheduling choices. A team that wants to protect the Seoul evening slot needs to agree on the earlier New York start. The calculation alone does not tell you which rule an existing invitation uses.
The late hours illustrate the conversion. Choose a meeting slot that the people on both sides can attend.
Why do you have to check the date as well as the hour?
A late-afternoon New York meeting lands on the next date in Seoul, so a copied hour can carry the wrong day as well as the wrong time. Copying only the hour can leave the date wrong.
| New York date and time (2026) | Seoul date and time (2026) | UTC date and time (2026) |
|---|---|---|
| Mon October 19, 5:00 PM | Tue October 20, 6:00 AM | October 19, 21:00 |
| Mon October 26, 5:00 PM | Tue October 27, 6:00 AM | October 26, 21:00 |
| Mon November 2, 5:00 PM | Tue November 3, 7:00 AM | November 2, 22:00 |
| Mon November 9, 5:00 PM | Tue November 10, 7:00 AM | November 9, 22:00 |
For example, a November 2 invitation described as “Monday at 5:00 PM New York” belongs on Tuesday morning in Seoul. Include the date beside each city when you confirm it.
How do you check the next occurrence before editing the series?
Before you change a series, open the first occurrence after November 1 and compare both local times and the UTC time with the hour the organizer meant to keep. Check the specific occurrence after November 1, then compare it with the organizer's intended local time.
- Read the full date and event time zone. Record the city used for the event, alongside the time shown on your own calendar.
- Check which local time should stay fixed. Ask the organizer whether the series should keep New York's hour or Seoul's hour.
- Compare the same occurrence on both sides. If the dates or times disagree, resolve that with the organizer before changing the series.
Google's Calendar event guide explains that recurring events use a single time zone to generate their occurrences. Check the event's zone alongside the local time shown on your calendar.
Microsoft's Outlook guide separates instructions for new Outlook, classic Outlook and the web version. It explains that attendees see their respective local times while meeting times are saved in UTC.
Those documents describe the products. The tables above are calculated examples; no Google Calendar or Outlook invitations were created, imported or changed for this article.
What should a two-city confirmation card contain?
The confirmation card below records the weekly rule, the next occurrence in both cities and its UTC time, so one message settles the change with the organizer. Replace the meeting title and use the date of your actual next occurrence.
Meeting: add your meeting title
Weekly rule: Monday, 09:00 in America/New_York
Next occurrence: 2026-11-02, 09:00 New York (UTC-05:00)
Same occurrence: 2026-11-02, 23:00 Seoul (UTC+09:00)
UTC check: 2026-11-02T14:00:00Z
Organizer confirmation: add the reply date
For a Seoul-fixed 10:00 PM occurrence on November 2, the matching values are 8:00 AM New York and 13:00 UTC. Update the rule and every line together.
Start with the next occurrence you need to attend. Send its two city dates and times to the organizer, and confirm which local hour the series should keep.
Calculation record. On November 2, 2026, we calculated the 12 examples using Python 3.10.11 zoneinfo with tzdata 2026.2. We checked each New York, Seoul and UTC value using Chromium 155.0.8059.39's Intl.DateTimeFormat: all 36 comparisons matched. The IANA time-zone database supplies named-zone rules. These checks verify time conversions, not app synchronization, recurrence exceptions, invitation delivery or anyone's availability. The cover is an original clock illustration of one calculated example.
Sources checked November 2, 2026: NIST daylight saving rules, Google Calendar event time zones, Outlook time-zone settings and IANA time zones.
About the author: JH-A, Charrette AI Room documents practical office workflows, examples and verification limits.
AI writing tools helped draft this post using the calculation record and official sources. A separate AI review checked the finished draft. See our editorial policy or contact us with a correction.
Related guides
If the agreed slot has to survive in a shared note that both sides can check, these two posts show how I record the evidence:
- How I Make Claude Code and Codex Share One Worklog
- REA for AI Agents: What It Can Prove About an App
Frequently Asked Questions
How many hours ahead is Seoul of New York after November 1, 2026?
Seoul is 14 hours ahead from November 2, 2026. New York moves to UTC−05:00 on November 1 and Seoul stays at UTC+09:00, so the 13-hour gap of October becomes 14 hours.
If a team keeps 10:00 PM in Seoul, what time is that in New York?
It becomes 8:00 AM in New York from November 2, 2026, where the same slot was 9:00 AM in October. The Seoul evening is protected and the New York morning moves one hour earlier.
Does the date change for a 5:00 PM New York meeting?
Yes. Monday at 5:00 PM in New York is Tuesday at 6:00 AM in Seoul before the clock change and Tuesday at 7:00 AM after it, so the date has to be confirmed beside each city.
Do Google Calendar or Outlook convert a recurring meeting automatically?
Both products keep one time zone for a recurring event and show each attendee their own local time. Whether that zone is the one the organizer meant still needs confirming, which is why the check here uses the next occurrence in both cities and its UTC time.
Comments
Post a Comment