Meeting Planner

Time Zone Math Explained Simply

UTC offsets and how they actually work — no jargon, just numbers

← Back to blog
Abstract geometric pattern with intersecting circular arcs representing global time zones and UTC offset calculations

Published August 2026 · 6 min read

If you've ever stared at a calendar invite and thought: "Wait, is that 3 PM my time or theirs?" — you've run headfirst into time zone math. It feels like a dark art, but it's actually built on two simple numbers and one straightforward rule. Once you understand how UTC offsets work, you'll never second-guess a meeting time again.

Here's time zone math, explained from first principles — using nothing more than addition, subtraction, and a single point of reference.

The one reference point everything orbits

Every time zone on Earth is defined by its distance from Coordinated Universal Time (UTC) — the global standard that replaced Greenwich Mean Time (GMT) in 1972. UTC is what the entire world agrees on. It never shifts for daylight saving. It doesn't care about politics, borders, or whether you prefer your clocks on the wall or in your pocket. It's just a number, ticking forward at the zero meridian.

The concept is simple: UTC sits at 0° longitude — the line that runs through Greenwich, London. Everywhere else is offset from it by some number of hours (and occasionally minutes). New York is UTC−5 during standard time. Tokyo is UTC+9. Mumbai is UTC+5:30. The offset tells you exactly one thing: how many hours to add or subtract from UTC to get local time.

That's the entire system. A plus sign means you're ahead of UTC (eastward). A minus sign means you're behind (westward). The range spans from UTC−12 (Baker Island, in the Pacific) to UTC+14 (Kiritimati, also in the Pacific — yes, you can be 26 hours ahead of your neighbor on the other side of the International Date Line).

The one equation that solves every scheduling problem

Here's the only formula you need:

Target local time = Your local time − Your UTC offset + Target UTC offset

Let's use a real example. You're in San Francisco (UTC−7 during PDT) and you need to find what time it is in Berlin (UTC+2 during CEST). It's 10 AM in San Francisco:

10:00 AM − (−7) + (+2) = 10:00 + 7 + 2 = 19:00 — that's 7 PM in Berlin.

Subtracting a negative gives you addition. Two negatives cancel out — and that's literally the trickiest part of the math. If you can handle minus-a-negative, you've mastered time zone conversion.

The same formula works in reverse. You're in Tokyo (UTC+9) and someone in New York (UTC−4 during EDT) suggests a 2 PM call. Is that reasonable?

2:00 PM − (+9) + (−4) = 14:00 − 9 − 4 = 1:00 AM Tokyo time. Not great.

This is why scheduling across 13 hours of offset requires deliberate planning — and why every distributed team eventually learns to think in terms of UTC anchor points.

Why it's "UTC" and not "CUT"

The abbreviation itself is a compromise. In English it would be CUT (Coordinated Universal Time). In French it's TUC (Temps Universel Coordonné). Neither side wanted to concede, so the International Telecommunication Union picked UTC — a letter sequence that matched neither language and instead followed the naming convention of Universal Time variants (UT0, UT1, UT2). The compromise stuck, and in 1967 UTC became the official global time standard.

Before UTC, the world ran on GMT — a time standard based on the mean solar time at the Royal Observatory in Greenwich. GMT served well enough in the age of steamships and telegraphs, but it was tied to Earth's rotation, which is irregular. The planet's spin slows down and speeds up by tiny amounts (milliseconds per day) due to tidal friction, atmospheric shifts, and even seismic activity. Atomic clocks, invented in 1955, exposed how imprecise astronomical time really was.

UTC solved this by combining the precision of atomic time with the practical need to stay aligned with the sun. It's now maintained by a weighted average of over 450 atomic clocks in 80+ laboratories worldwide, coordinated by the International Bureau of Weights and Measures (BIPM) in Paris. When atomic time drifts more than 0.9 seconds from Earth's rotation, a leap second is inserted. Since 1972, 27 leap seconds have been added — the most recent on December 31, 2016.

Offsets aren't always whole hours

Most time zones differ from UTC by a round number of hours, but not all. Several countries use half-hour offsets:

Nepal takes it further: UTC+5:45. It's the only country with a 45-minute offset, chosen so that noon in Nepal aligns with solar noon at Mount Gauri Shankar. The Chatham Islands of New Zealand use UTC+12:45 during standard time — creating a 45-minute gap from mainland New Zealand (UTC+12).

These fractional offsets are why mental time zone math fails. You can't just "count back 9 hours" from Tokyo to New York when India sits in the middle at +5:30 and Afghanistan at +4:30. The pipeline is: Tokyo +9 → India +5:30 → Iran +3:30 → London +1 → New York −4. Without a tool or a reference table, the half-hour offsets create subtle errors that compound across long chains.

Daylight saving: when the offset changes

If UTC offsets were static, time zone math would be a solved problem. But roughly 71 countries observe daylight saving time, and each one flips its offset by one hour twice a year — on different dates. During DST, the offset shifts by +1 hour (e.g., New York goes from UTC−5 to UTC−4).

The complication is the staggered transition schedule. In 2026, the United States and Canada spring forward on March 8. Most of Europe waits until March 29 — creating a three-week period where the US/Europe offset is one hour narrower. A meeting that works in February (New York 9 AM / London 2 PM) might not work during those three weeks in March (New York 9 AM / London 1 PM — doable, but shifted) — and if someone booked it based on the February math, they'll show up at the wrong time.

The practical takeaway: never memorize another location's offset. Memorize the formula instead. Look up the current offsets when you need them, plug them into the equation, and check whether DST is active for both locations. A good time zone meeting planner handles this automatically — it shows you the current offsets, flags upcoming DST transitions, and lets you visualize the overlap on a 24-hour timeline.

One mental shortcut: think in UTC

If you regularly schedule across three or more time zones, the most reliable mental model is to think in UTC. Instead of converting from Location A to Location B to Location C, convert everything to UTC and then back out:

  1. Convert your local time to UTC (subtract your offset).
  2. Think about the meeting in UTC terms: "The meeting is at 14:00 UTC."
  3. Convert UTC to each attendee's local time (add their offset).

This is how airlines, military operations, and software systems handle global scheduling. Pilots file flight plans in UTC ("Zulu time"). Servers log in UTC. The International Space Station runs on UTC. When you anchor everything to a single unmoving reference point, you eliminate the domino effect of chained conversions.

You don't need to memorize every offset. You just need to know the formula and have a way to look up the current numbers. The math is addition and subtraction. The hard part isn't the arithmetic — it's remembering to do it at all, and catching the DST transitions before they catch you.

Done doing time zone math in your head? Drop your team's cities into the planner and see the overlap instantly — no arithmetic required. Try the Time Zone Meeting Planner →