Guides, explainers and practical tips about time zones, world clocks, and international scheduling — for travellers, remote workers, and the simply curious.
If you work with an international team, you've almost certainly experienced the meeting time zone problem. Someone books a call for "10 AM" — but 10 AM where? In New York? London? Sydney? A simple misunderstanding can mean someone joins two hours early, two hours late, or misses the call entirely.
This guide walks you through the most reliable methods for scheduling across time zones, avoiding daylight saving traps, and keeping your global team on the same page.
The simplest habit you can develop is anchoring every meeting time to UTC — the universal time standard that doesn't change for daylight saving. When you tell your team "our weekly sync is Tuesdays at 14:00 UTC," everyone can convert to their own local time and there's no ambiguity. UTC is the time used by aviation, international finance, and global internet infrastructure for exactly this reason.
For example, 14:00 UTC is: 9:00 AM New York (EST), 2:00 PM London (GMT), 3:00 PM Paris (CET), 7:00 PM Dubai (GST), 10:00 PM Singapore (SGT).
Memorising a few key differences helps enormously. Here are the most common ones for global teams:
The trickiest weeks of the year for international scheduling are the ones around Daylight Saving Time transitions — and they don't happen at the same time everywhere. The US typically switches in early March, while Europe switches in late March. This creates a 2-3 week window where the gap between, say, New York and London is only 4 hours instead of 5.
Similarly, Australia and New Zealand observe DST in reverse (their summer is October to April), which creates seasonal shifts in their time gaps with Asia and Europe. Always double-check the actual current time difference before sending meeting invites in October and March.
When sending calendar invites, include the meeting time in at least two or three time zones in the event description. For example: "Product sync — 15:00 UTC (10:00 AM ET / 3:00 PM GMT / 11:00 PM SGT)." This takes 30 seconds and eliminates confusion entirely.
Most calendar apps (Google Calendar, Outlook) also allow you to display a secondary time zone alongside your primary one — a feature that's well worth enabling if you work internationally.
If your team spans three or more continents, finding a time that works for everyone is genuinely difficult. The "golden window" that works best for US East Coast, Europe, and Asia Pacific is roughly 08:00–10:00 UTC — which lands in the morning for Europe, early afternoon for the Gulf, and late afternoon/early evening in Southeast Asia, while catching the US East Coast before 6:00 AM (which is usually too early unless absolutely necessary).
💡 Quick tip: Use WhatTimeIsItIn...? to check live times across all your team's cities at once, then use the search bar to compare across regions before locking in your meeting time.
No time zone is inherently more important than another, and fairness matters for team morale. If your team is split between San Francisco and Tokyo, somebody is always going to be on a call at an awkward hour. The equitable solution is to rotate which team takes the early morning slot — alternating so that the burden is shared over time. Document this in your team norms so it's transparent and expected.
India Standard Time is UTC+5:30 — and that half-hour offset confuses people every time they see it. Why 5 hours and 30 minutes? Why not simply UTC+5 or UTC+6? The answer is a fascinating mix of geography, colonial history, and national compromise.
India is a large country, stretching approximately 3,000 kilometres from its westernmost point (near Dwarka in Gujarat) to its easternmost (near Arunachal Pradesh). In pure longitude terms, India spans from roughly 68°E to 97°E — a difference of about 29 degrees, or nearly two full time zone widths.
If India followed the conventional system of one time zone per 15° of longitude, it would naturally split into two zones: roughly UTC+5 for the west and UTC+6 for the east. In fact, under British rule, three separate time zones were used: Bombay Time (UTC+4:51), Calcutta Time (UTC+5:54), and Madras Time (UTC+5:21).
When India was unified under British administration, the Railways — one of the great connective tissues of the subcontinent — needed a single standardised time for their timetables. In 1884, the Indian railways adopted Madras Time (UTC+5:21) as the standard railway time, as Madras was considered to be roughly in the geographical centre of the country's population.
After independence in 1947, the new Indian government needed to decide on a single national time. Rather than splitting the country into zones (which would have created practical complications across such a newly unified nation), they chose a single compromise offset: UTC+5:30, splitting the difference between Calcutta and Bombay time. The 30-minute increment placed India's solar noon close to the astronomical noon at roughly 82.5°E longitude — a meridian that runs through Mirzapur in Uttar Pradesh, which is still officially considered the reference meridian for India Standard Time.
Sri Lanka also uses UTC+5:30, making it one of the few countries in the world to share India's unusual offset. Sri Lanka has historically used the same time zone as India due to their close geographic and economic ties, despite being geographically positioned where UTC+6 might be more astronomically appropriate.
Every few years, someone in India proposes splitting the country into two time zones — particularly politicians from the northeast, where the sun rises as early as 4:00 AM in summer while the clock still says 4:30 AM. The northeastern states effectively operate on an informal "Tea Garden Time" — starting work an hour or two earlier than the rest of the country to align with daylight.
Proponents of splitting argue that a two-zone system would improve productivity, reduce energy waste, and better align daily rhythms with natural light. Opponents argue that a single national time zone is a symbol of unity and that the practical complications of splitting train timetables, television schedules, and government offices would outweigh the benefits.
💡 India is not alone in this — Nepal goes even further with UTC+5:45, a 15-minute offset that makes it unique in the world. The reason is similar: a desire to be distinct from India while sitting geographically between India and Bangladesh.
Crossing time zones is one of the more disorienting aspects of long-haul travel. Whether you're flying from Dublin to Dubai, New York to Tokyo, or Sydney to London, your body's internal clock — the circadian rhythm — takes time to adjust to the new light-dark cycle at your destination. Here's everything you need to know about managing the transition.
Jet lag occurs when there is a misalignment between your body's internal clock (set to your home time zone) and the external clock at your destination. Your circadian rhythm regulates sleep, hunger, hormone production, body temperature, and dozens of other biological processes. When you cross multiple time zones rapidly — as you do on a flight — these processes are still operating on home time while the external world has shifted.
The severity of jet lag depends on several factors: the number of time zones crossed, the direction of travel (eastward travel is generally harder than westward), your age (older people tend to adapt more slowly), and your individual physiology. Crossing more than 3 time zones is generally enough to cause noticeable jet lag symptoms in most people.
Travelling east is harder than travelling west for most people, because it requires your body to advance its clock — going to sleep and waking up earlier than your natural rhythm wants. Westward travel requires delaying the clock, which most people find more natural. This is why a flight from London to New York tends to feel easier than the return flight.
The toughest time zone crossings are those that involve the most hours of shift combined with long flight times that don't allow natural adjustment:
For important trips (business meetings, weddings, competitions), it's worth starting to adjust your schedule 3–5 days before departure. If you're flying east, go to bed 30–60 minutes earlier each night. If flying west, push your bedtime later. Combined with daylight management, this can significantly reduce the severity of jet lag on arrival.
💡 Before you travel, check WhatTimeIsItIn...? to see the exact current time at your destination and compare it to home. Knowing you're 5.5 hours behind helps you plan your pre-trip adjustment strategy.
China is the fourth-largest country in the world by area, stretching roughly 5,200 kilometres from east to west. By any geographical logic, it should span four or five time zones. Yet the entire country — from Shanghai on the Pacific coast to Kashgar on the edge of Central Asia — runs on a single time: Beijing Standard Time, UTC+8.
This is one of the most striking examples in the world of time being used as a political instrument rather than a geographical convenience.
China was not always on a single clock. Before 1949, the Republic of China used five official time zones: Kunlun Time (UTC+5:30), Sinkiang-Tibet Time (UTC+6), Kansu-Szechuan Time (UTC+7), Chungyuan Standard Time (UTC+8), and Changpai Time (UTC+8:30). These roughly followed the natural division of the country by longitude.
When the People's Republic of China was established in 1949, Mao Zedong's government made a deliberate decision to unify the entire country under a single time zone: Beijing Standard Time (UTC+8). The rationale was explicitly political — a unified clock was seen as a symbol of national unity and central authority. The message was clear: China is one country, and it operates on one time.
This decision has never been reversed, and it remains official policy today despite decades of debate about the practical consequences.
The most dramatic consequences of this policy are felt in Xinjiang, in China's far northwest. The region sits at roughly the same longitude as Pakistan and Afghanistan — both of which use UTC+5 or UTC+5:30. Astronomically, Xinjiang's noon falls at around 3:00 PM on the Beijing clock, and sunrise in winter can be as late as 10:00 AM.
The practical result is that much of Xinjiang effectively runs on two parallel time systems. The majority Uyghur population widely uses "Xinjiang Time" (UTC+6) — two hours behind Beijing time — for daily life, social interactions, and local business. Government offices, railways, and airlines, however, operate strictly on Beijing Time. A local resident might tell you it's 10 AM, while the government office they need to visit won't open for another two hours according to its clock.
This dual-clock reality is a source of significant practical inconvenience and has deeper political resonances in a region with a complex relationship with Beijing.
From a purely practical standpoint, a two-zone system — perhaps UTC+8 for the east and UTC+6 for the west — would significantly improve quality of life in western China. Sunrise and sunset times would align more naturally with the working day, reducing energy waste (people in Xinjiang use more artificial lighting than necessary due to the offset) and improving the alignment of social rhythms with daylight.
China's government has consistently resisted this suggestion on the grounds of national unity. Given the political sensitivity of Xinjiang specifically, a separate time zone for the region is unlikely to be adopted in the foreseeable future.
💡 China is not entirely unique in this approach — India also uses a single time zone despite its geographic spread, though India's case is less extreme. The USA, Canada, Russia, Australia, and Brazil all use multiple time zones across their territories.
For digital nomads who work with clients or employers in a specific region, the choice of base city isn't just about cost of living and quality of life — it's about time zones. Being in the wrong time zone can mean working exclusively at night, missing crucial meetings, or being permanently out of sync with your team.
Here's a breakdown of the best base cities by region, with honest assessments of the time zone trade-offs.
Best bases: Lisbon, Dublin, London, Amsterdam
Western Europe is the sweet spot for working with US clients, particularly those on the East Coast. At UTC+0 to UTC+1, you share working hours from roughly 2 PM to 6 PM your time with the US morning. You can get your own deep work done in the morning, then be available for US meetings in your afternoon. Lisbon in particular has become enormously popular among American remote workers and those servicing US clients, offering a low cost of living, excellent weather, and a startup-friendly visa program — all while sitting in the optimal time zone overlap.
For West Coast clients (Los Angeles, San Francisco), the gap from Europe is larger (8–9 hours), making it harder. Cities in the Americas — particularly Medellín, Mexico City, or Buenos Aires — are better choices for US West Coast alignment.
Best bases: Tbilisi, Chiang Mai, Bali
Southeast Asia (UTC+7 to UTC+8) provides a surprisingly workable overlap with Europe, especially Central and Eastern Europe. At UTC+7, there's a 6-hour gap with CET — meaning your mornings (8–11 AM) overlap with European afternoons (2–5 PM). Bali (UTC+8) and Bangkok (UTC+7) have large established nomad communities partly for this reason.
Tbilisi, Georgia (UTC+4) is an underrated option: it's 2–3 hours ahead of Western Europe, which means a European afternoon meeting falls at a comfortable late afternoon for you. Georgia's digital nomad visa, low cost of living, and excellent food scene make it increasingly popular.
Best bases: Tokyo, Singapore, Bali, Ho Chi Minh City
Singapore (UTC+8) is the classic choice for APAC workers — it overlaps perfectly with major Asia-Pacific business hubs including Hong Kong, Kuala Lumpur, Manila, and Taiwan. Tokyo (UTC+9) is ideal for Japanese clients and also works well for Korean and Australian clients. Bali (UTC+8) offers a lower cost base while sharing Singapore's time zone.
If your work is mostly asynchronous — Slack messages and email rather than live calls — the time zone matters much less. In that case, optimise purely for quality of life and cost. The cities that consistently top nomad rankings for these reasons regardless of time zone include: Medellín (Colombia), Chiang Mai (Thailand), Tbilisi (Georgia), Budapest (Hungary), Porto (Portugal), and Ho Chi Minh City (Vietnam).
💡 Use the Time Zone Map on WhatTimeIsItIn...? to visually compare your potential base city against your clients' locations, and check the UTC Offsets page to find the exact hour difference.
It's easy to take time zones for granted — of course London is 5 hours ahead of New York. But for most of human history, there was no such thing as a time zone. Every town and city kept its own time based on the position of the sun, and the idea of a globally coordinated system of time was not just unnecessary — it was technologically impossible. The story of how we got from there to here involves railways, wars, geographers, and a surprising amount of political drama.
Before the 19th century, time was purely local. Every city, town, and village kept its own "local solar time" — the time indicated by a sundial, defined by when the sun was highest in the sky (local noon). This worked perfectly well when the fastest form of communication was a horse, and travel between cities took days. A 20-minute difference between neighbouring towns was irrelevant if you couldn't travel between them faster than a day's ride.
In Britain alone, there were hundreds of different local times. London was about 10 minutes ahead of Bristol, and about 24 minutes ahead of Plymouth. This was not a practical problem until the railways arrived.
The Great Western Railway opened in 1838 connecting London to Bristol. Almost immediately, its operators realised they had a problem: how do you publish a timetable when the clocks at each end of the line show different times? A train departing London at 9:00 AM arrived in Bristol at what Bristol clocks showed as 8:49 AM — which was deeply confusing to passengers and created genuine safety risks as more railways opened and the network became more complex.
In 1840, the Great Western Railway adopted "Railway Time" — London time, based on Greenwich — for all its timetables. Other British railway companies quickly followed. By 1847, most British railways were using Greenwich time, and in 1855 the Electric Telegraph Company began broadcasting Greenwich time signals to towns across Britain. By 1880, "Greenwich Mean Time" was made the legal standard time for all of Great Britain.
The United States faced the same problem on a vastly larger scale. In 1870, American railways were operating on approximately 80 different local times — one for each major city on their routes. Scheduling was nightmarish, accidents were a genuine risk, and passengers could never be sure what time a timetable was referring to.
American railway engineer Charles Dowd proposed a system of four time zones for the United States in 1870, each one hour apart. His proposal was largely ignored for over a decade. It was eventually the railway industry itself — not the government — that implemented a standardised system. On 18 November 1883, American and Canadian railways simultaneously switched to a four-zone system: Eastern, Central, Mountain, and Pacific. The event was known as "the Day of Two Noons" because clocks in some cities were moved back, meaning the sun appeared to reach its peak twice in the same day.
With national systems emerging in various countries, there was a growing need for an international standard. In October 1884, delegates from 25 nations gathered in Washington DC for the International Meridian Conference. The central question: which meridian should serve as the world's prime meridian — the reference line of 0° longitude from which all other times would be calculated?
The Greenwich Meridian, running through the Royal Observatory in London, was the most widely used reference for navigation and already served as the basis for British and most colonial time systems. The conference voted 22–1 (with 2 abstentions) to adopt Greenwich as the universal prime meridian. France — which had historically used the Paris Meridian — was the only country to vote against, and pointedly continued using Paris Mean Time until 1911.
The 1884 conference established the principle, but adoption was gradual. Russia didn't adopt standard time zones until 1919, following the revolution. India unified its various colonial time zones in 1906. China moved from five zones to one in 1949. Saudi Arabia switched from "local solar time" (where noon was always 12:00 regardless of the clock) to a standard offset as recently as 1968.
Today, all 195 countries in the world use a UTC-based time system — one of the most genuinely universal standards in human history. The fact that you can tell someone anywhere in the world "the meeting is at 14:00 UTC" and they can immediately translate it to their local time is a remarkable piece of global coordination that most of us take entirely for granted.
💡 The Royal Observatory in Greenwich, London — the origin point of UTC 0 — is open to visitors. You can stand with one foot in the Western Hemisphere and one in the Eastern, straddling the Prime Meridian line. The green laser beam fired northward from the observatory marks the meridian line on London's sky at night.