Set a call time across Riyadh, London and Manila

Why you’d do this

Three cities, one call. Riyadh is three hours ahead of UTC, Manila is eight, and London is either zero or one depending on the time of year. Doing that in your head works until the week the clocks change in London, when a call you have run at the same local time for months quietly lands an hour away from where everyone expects it.

Time Zone Converter takes one moment and shows it on every city’s clock, with the date change spelled out. Flight Time Calculator does the related job when someone is travelling: it adds the scheduled flight duration to the departure and reads the arrival on the destination city’s own clock.

How, with the named tool

Time Zone Converter

1. Stay on the Convert tab. Choose the From city, then a Date and a Time, or tap Use the time now.
2. Read The same moment elsewhere. Each pinned city shows its local time, its UTC offset, and whether it lands the same day, the next day or the day before. Copy the times takes the list.
3. Riyadh, London and New York are pinned to begin with. Manila is in the built-in list of 194 cities, so search under Add a city and tap the result to pin it; press × beside a city under Your cities to remove one.
4. Switch to Meeting planner, set the Meeting date and the Working hours start and Working hours end, and read across the hour strip. Hours inside working hours are marked in every city at once; tap Pick this hour on one that suits everyone.

An example: Thursday 12 November 2026, 15:00 in Riyadh is 12:00 in London (UTC+0) and 20:00 in Manila (UTC+8). The same 15:00 Riyadh call on 15 July is 13:00 in London (UTC+1) and still 20:00 in Manila.

Flight Time Calculator

1. Pick the From and To cities, then the Departure date and Departure time.
2. Enter the Flight duration in Hours and Minutes — use the scheduled time printed on the ticket.
3. Tap Add a leg for a connection and set its connection type.
4. Read Your itinerary: each arrival is in the arrival city’s local time, with any date change shown, plus Door to door, In the air and On the ground totals. Copy the itinerary takes it all.

For instance, leaving Riyadh at 23:10 on 12 November 2026 with a scheduled 6 h 20 min flight (an illustrative duration, not a real timetable) lands at 02:30 London time on 13 November, which the tool shows as the next day.

What to watch for

Daylight saving is not symmetric. Saudi Arabia does not observe it, so Riyadh stays at UTC+3 all year — the tool says exactly that. The Philippines does not use it either, so Manila stays at UTC+8. London does: it is UTC+0 in winter and UTC+1 in summer, switching on the last Sundays of March and October. So the Riyadh–Manila gap is always five hours, while the Riyadh–London gap is two hours in summer and three in winter, and the London–Manila gap is seven hours in summer and eight in winter. When you schedule a recurring call, check the dates either side of the change.

The maths runs on one moment, not on a pile of offsets. The tool turns your date and time into a single instant, then reads that instant on each city’s clock using the time zone database in your own device. It does not store an offset next to a city, because an offset depends on the date. That is why the result stays right across a clock change — and also why it depends on how current your device’s database is.

Clock-change nights can break a local time. When clocks jump forward, a local time such as 01:30 in London may not exist that night; when they fall back, it happens twice. The tool tells you which, and for a repeated time it asks which moment you meant, using the earlier one unless you change it.

Say the time in a form no one can misread. The tool’s Copy the times output lists each city with its date, time and UTC offset, for example Riyadh 2026-11-12 15:00 (UTC+3). That is the safest thing to paste into an invitation, because it pins the exact moment. If you write it yourself, an ISO instant such as 2026-11-12T12:00:00Z means the same moment for everybody; the tool does not produce that exact format.

Flight durations are what you type. There are no schedules or route data inside the tool, so it is only as good as the duration you enter. It reads the published gate-to-gate time, and the date line and any daylight-saving change are already inside the arithmetic.

FAQ

Does Saudi Arabia change its clocks?

No. Saudi Arabia does not observe daylight saving time, so Riyadh’s offset is the same all year. London does change, so the gap between them moves by an hour twice a year.

Why does the same call time look different in London after October?

Because London leaves summer time on the last Sunday of October and moves from UTC+1 to UTC+0. Riyadh stays at UTC+3, so the gap grows from two hours to three.

Does the flight calculator know how long my flight takes?

No. You enter the scheduled duration from your ticket. The tool adds it to the departure and shows the arrival on the destination city’s clock, with the date change spelled out.