FREE TOOL — TIME ZONES
Landing at 2 pm means nothing until you know whose 2 pm. The offsets that matter for the routes most of our readers fly.
Pick any two airports to see the time difference between them — and what the clock says at the other end when you take off.
🛫 Step 1 — Your route
🕐 Step 2 — When do you leave?
⚠️ Estimate only: based on great-circle distance and typical average speeds. Real flight times vary with winds, routing and airline schedules — westbound flights often take longer. Time differences use standard offsets; daylight saving can shift the local clock by an hour.
| City | UTC offset | Daylight saving |
|---|---|---|
| Dhaka | UTC+6 | None |
| Dubai | UTC+4 | None |
| Doha | UTC+3 | None |
| Istanbul | UTC+3 | None |
| Delhi | UTC+5:30 | None |
| Bangkok | UTC+7 | None |
| Singapore | UTC+8 | None |
| Kuala Lumpur | UTC+8 | None |
| London | UTC+0 (UTC+1 in summer) | Yes |
| Frankfurt | UTC+1 (UTC+2 in summer) | Yes |
| New York | UTC−5 (UTC−4 in summer) | Yes |
| Toronto | UTC−5 (UTC−4 in summer) | Yes |
| Sydney | UTC+10 (UTC+11 in summer) | Yes — southern hemisphere |
| Honolulu | UTC−10 | No |
| Anchorage | UTC−9, −8 in summer | Yes |
| Los Angeles | UTC−8, −7 in summer | Yes |
| Denver | UTC−7, −6 in summer | Yes |
| Mexico City | UTC−6 | No |
| Chicago | UTC−6, −5 in summer | Yes |
| Miami | UTC−5, −4 in summer | Yes |
| Bogotá | UTC−5 | No |
| São Paulo | UTC−3 | No |
| Madrid | UTC+1, +2 in summer | Yes |
| Paris | UTC+1, +2 in summer | Yes |
| Amsterdam | UTC+1, +2 in summer | Yes |
| Rome | UTC+1, +2 in summer | Yes |
| Cairo | UTC+2, +3 in summer | Yes |
| Johannesburg | UTC+2 | No |
| Nairobi | UTC+3 | No |
| Addis Ababa | UTC+3 | No |
| Riyadh | UTC+3 | No |
| Tehran | UTC+3:30 | No |
| Karachi | UTC+5 | No |
| Mumbai | UTC+5:30 | No |
| Colombo | UTC+5:30 | No |
| Jakarta | UTC+7 | No |
| Manila | UTC+8 | No |
| Hong Kong | UTC+8 | No |
| Taipei | UTC+8 | No |
| Beijing | UTC+8 | No |
| Seoul | UTC+9 | No |
| Tokyo | UTC+9 | No |
| Perth | UTC+8 | No |
| Brisbane | UTC+10 | No |
| Melbourne | UTC+10, +11 in summer | Yes |
| Auckland | UTC+12, +13 in summer | Yes |
Your flight lands in London at 18:40 local. In summer London is UTC+1 and Dhaka is UTC+6, so it is 23:40 back home — message the family before they sleep. Here is the maths behind that answer:
Step 1 — Note both offsets. London in summer keeps UTC+1; Dhaka keeps UTC+6 all year.
Step 2 — Subtract the offsets. 6 − 1 = 5 hours, and Dhaka is the city ahead.
Step 3 — Add the gap to the local time. 18:40 + 5 hours = 23:40 in Dhaka.
1. Tickets always show LOCAL times — the local time at each airport, never your home time. A 13:30 arrival means 13:30 where you land.
2. Your phone updates itself when you land; your body clock does not. Give yourself roughly a day for every few time zones crossed before you start feeling normal again.
3. Crossing the Pacific, you can land “before” you took off — on the local clock, at least. The calendar day changes as you cross the date line, but the clock maths never lies: the elapsed time is always real.
Always local. The departure time is the local time at the departure airport, and the arrival time is the local time at the arrival airport. An airline app may also show the time back home, but the times printed on your ticket are local to each airport.
UTC (Coordinated Universal Time) is the world’s reference clock. Every time zone is described as hours ahead (+) or behind (−) UTC — Dhaka is UTC+6 all year round. Airlines plan schedules in UTC so there is never confusion about which clock a time belongs to.
On very long routes the time-zone shift can be bigger than the flight time itself, so the local clock — and sometimes the calendar date — at arrival can be earlier than when you left. The flight still took exactly the hours shown; only the clocks moved.