Google Calendar While Traveling: Same Meeting, Different Clock Time

Your meeting is still scheduled for the same instant after you land. If it starts at 10 a.m. in Seoul, you join at 8 a.m. in Bangkok. Moving it to 10 a.m. Bangkok time would put the calendar appointment two hours later, at noon in Seoul.

The confusing part is that a wrongly entered booking can look similar. A Bangkok reservation entered as 10 a.m. Seoul time also appears at 8 a.m. in Bangkok. That entry needs correcting. The first step is to compare the event with the original agreement, including its city and date.

A traveler asking about Google Calendar described events shifting by a day, then finding the calendar awkward to read after disabling the device time zone. Their follow-up concerned flight times. Keeping every appointment in its original calendar slot would not solve all three problems.

A different day can still mean the same instant

Google’s calendar model describes timed events through their start and end points. Different time-zone expressions can represent the same instant. An all-day event instead uses dates; it does not represent a flight’s precise departure time.

Consider these calculated examples for October 2026. Seoul uses UTC+9 and Bangkok UTC+7. Each row represents one appointment, viewed from two locations.

The second call crosses a date boundary when displayed in Bangkok. Moving it to October 28 simply to restore its old date would change the appointment. When confirming it with someone else, include the location: “October 28 at 12:30 a.m. Seoul time” gives both people something precise to compare.

The third row also explains why a booking made for Bangkok can appear at noon while you are still at home in Seoul. That is the expected conversion. It is not a request to arrive two hours after the local reservation time.

Enter the booking’s city, then its date and time

For a destination appointment, use the city and clock time printed on the confirmation. On the web, create an event, open More options and select Time zone beside the time fields. Google’s time-zone instructions cover both new events and editing an existing event’s zone.

For the Bangkok booking above, choose Bangkok and enter 10 a.m. on the reserved date. There is no need to mentally convert that to noon first. Applying a manual conversion and then choosing the destination’s zone can shift the entry again. After saving, compare the resulting display with the table rather than replacing the visible number with the one from the confirmation.

For a flight, select Use separate start and end time zones. Enter the departure city’s local date and time at the start, and the arrival city’s local date and time at the end. On the return journey, check both cities again.

For example, imagine an itinerary departing Seoul at 6 p.m. on October 27 and arriving in Bangkok at 10 p.m. that day. The arrival corresponds to midnight on October 28 in Seoul, so the elapsed interval is six hours. Subtracting the two printed clock readings gives four hours because they belong to different zones. This is an illustrative calculation, not a published flight schedule.

An all-day “Bangkok trip” entry can mark your travel dates, but it cannot replace the timed flight entry. Keep the departure information where it can be compared with the ticket. A trip label, an airport transfer and a flight can legitimately occupy different parts of the calendar.

Use the local clock without losing sight of home

In the Google Calendar app, open Menu → Settings → General → Use device time zone. Google documents this setting for both Android and iPhone and iPad. Enabled, it updates the zone automatically as you travel; disabled, it lets you choose one. These are Google Calendar instructions, including on iPhone.

Local display time makes it easier to compare an appointment with the clock around you. Keeping Seoul as a fixed display zone may suit a work schedule organized around Seoul, but its 10 a.m. must still be read as Seoul time. Switching off automatic updates does not repair a booking that was entered with the wrong zone.

On the web, Settings → General → Time zone controls the primary display zone. Additional time-zone columns let you compare home and destination hours without creating duplicate meetings. Google’s September 2026 expansion supports up to three zones in Day, Week and custom multiday views, plus Find a Time. The feature includes custom labels and personal Google accounts.

For a Bangkok stay, put Bangkok and Seoul beside each other; add London if a third team is involved. One event then lines up with several clock readings. The three-column feature is documented for the web, so the mobile instructions above do not promise an identical grid on a phone.

A weekly team meeting and an 8 a.m. routine move differently

A recurring meeting needs an agreed reference zone. “Every Friday at 9 a.m. London time” follows London’s clock. When British Summer Time ends, participants elsewhere may see a different hour even if they have not traveled.

The UK government’s 2026 dates put the autumn clock change on October 25. A London 9 a.m. meeting therefore gives these calculated attendance times:

If the agreement is instead “5 p.m. Seoul time,” the London attendance time changes. Confirm which city anchors the meeting before correcting the series. Inspect actual occurrences on both sides of the transition, since an organizer may also have moved one individual meeting.

A personal routine has a different purpose. Reading at 8 a.m. wherever you are means moving the scheduled instant when you travel. An 8 a.m. Seoul event points to 6 a.m. in Bangkok; that preserves its original timing but misses your intended local morning.

For a short trip, one approach is a separate Bangkok 8 a.m. series with an end date, while removing the overlapping home-series occurrences for that period. For a permanent move, adjust future occurrences to the new local schedule. Check the last travel day and the first day back so the temporary series does not continue after you return.

Google’s recurring-event editor asks which events a saved change should affect. Read that scope before applying a change. A trip lasting several days does not call for moving an entire history of appointments.

Shared meetings also have editing permissions. The event permissions guide allows organizers to grant guests permission to change times. Having that permission does not turn a meeting edit into a private display preference. Agree on a new meeting time with the organizer when travel changes your availability.

Fix the incorrect entry, then compare it with the confirmation

If your team meetings line up but one tour is two hours early, open that tour first. Compare three things: the reservation’s city, date and time; the event’s stored zone and time; and the zone used by your calendar view. Correcting a Bangkok 10 a.m. booking mistakenly entered as Seoul 10 a.m. should produce Bangkok 10 a.m. and Seoul noon.

For an automatically added Gmail booking, open its original email. Google’s Gmail-events help identifies View confirmation on the web and View source email in the app. Compare the latest reservation update as well as the original confirmation. Editing the calendar entry does not change the booking with the airline or restaurant.

If an event is missing entirely, or the web and app hold different details for the same account, use Google’s sync troubleshooting steps: check connectivity, the account and the calendar’s visibility and sync settings. Clearing app data can lose unsynced information, so a different displayed hour alone is no reason to start there.

Reopen the corrected entry in the destination’s zone and compare its date and time with the confirmation. For a recurring meeting, also check the next actual occurrence in the organizer’s reference zone.