
Recovering from jet lag is a process that, well, takes time. But that only works within about 4 or 5 hours difference. A flight from New York to Tokyo, on the other hand, leaves you with a 13-hour difference, which effectively means reversing your sleep/wake schedule.įlights from east to west, where you gain a few hours, are usually a bit easier, as most people find it easier to stay up a little later than to go to bed earlier. Flying from Paris to Johannesburg, while it might take you 15–20 hours, wouldn't leave you very jetlagged because there's only 1 hour time difference. Where flying isn't concerned, it isn't the length of the flight that matters.
London gmt time zone plus#
The fatigue from travelling plus the mismatch with local time can leave you ready to fall asleep just after lunch, or being wide awake in the middle of the night, knowing that dawn is still several hours away. Jet lag is also compounded by the fact that long hours spent on a plane can cause you to sleep too much, or not enough, possibly at the wrong time of day relative to where you departed from. It's caused by rapid travel across time zones. Jet lag is a mismatch between your body clock and the local time wherever you are.

If you travel has time zone complexities or possible impacts on your health or comfort, consult an expert as you plan it.

west coast to Japan or Hong Kong in late evening can land you there in the morning two calendar days later. Starting a 12–15 hour flight from the U.S.Crossing the International Date Line can cause confusion about on what date you'll arrive, e.g.,:.You may miss important obligations simply by not understanding what will be the correct local time as you travel.Your "body clock" may experience some stress as you "tell" it to meet business appointments, tours and other obligations perhaps a few or several hours different from the hours you normally rest.You need to take some care when planning trips that span time zones, e.g.,: (Note: The total span of time zones covers more than 24 hours because the Date Line jogs westward and eastward to keep certain national island groupings on the same calendar day, although they are not within a single time zone.)
London gmt time zone full#
Crossing the Date Line going eastward, clocks are turned back a full 24 hours, and vice versa in the opposite direction. UTC+4) zones west of UTC and east of the Date Line are specified by the number of hours behind UTC (e.g. Time zones east of UTC and west of the International Date Line are specified by the number of hours ahead of UTC (e.g. It comes from the nautical system in which each time zone was assigned a letter. The "Z" is for "zero", and "Zulu" is the two-way radio pronunciation of "Z". UTC is also sometimes called Z or Zulu time. UTC used to be called GMT (Greenwich Mean Time), after the Royal Observatory located in the Greenwich area of London. Tackling this made me wonder, are there any formal ways or de facto standards for expressing a coordinated meeting time across multiple timezones? (For human readers who don't want to calculate or look things up.This is a list of countries, regions, and territories grouped by time zone.Īlthough many time zones have descriptive names used by people in them, they are least ambiguously identified by their relationship to UTC (Universal Time, Co-ordinated). This maintains an unambiguous universal expression, and more readable local times. I was thinking of the following instead:Ĭan we meet at 11h00 UTC (7am New York, 12pm London, 6pm Tokyo)? And on reflection it is difficult to read, and comes across as centric to my own timezone (which is inappropriate for a virtual meeting). but it turns out many people don't know or recognise the obscure abbreviation for their own time zone so they'd email back to confirm. Previously I would express times like this:Ĭan we meet at 07h00 EDT (11h00 UTC, 12h00 BST, 18h00 JST)? time to calculate or double-check timezone differences), I include the time in all relevant timezones in the body of the email. Due to differences in recipients' email clients and resources (e.g.

I occasionally coordinate virtual meetings across multiple timezones.
