World Time Zones | Worksheet - Free Printable

Let’s solve each question step by step using the time zone map.

We are told:
- There are 24 time zones.
- Each time zone is one hour apart.
- Moving east → add one hour per time zone.
- Moving west → subtract one hour per time zone.
- Coordinated Universal Time (UTC) is at 0° longitude (the prime meridian).

The map shows UTC offsets from -11 to +12, with vertical lines marking each time zone.

---

Question 1:
> Christina lives in London, England. If she updates her blog at 7 p.m., what time will it be when she uploads for her readers in California?

Step 1: Find London’s time zone.
London is on the Prime Meridian → UTC+0 (or just UTC).

Step 2: Find California’s time zone.
California is on the West Coast of the U.S. Looking at the map, the western U.S. (including California) is around UTC-8 (Pacific Time).

Step 3: Calculate the time difference.
From UTC+0 to UTC-8 → that’s 8 hours behind.

So if it’s 7 p.m. in London, subtract 8 hours:

7 p.m. minus 8 hours = 11 a.m. (same day)

Wait — let’s double-check:
7 p.m. = 19:00
19:00 - 8 hours = 11:00 → 11 a.m.

✔ Correct.

---

Question 2:
> If newscasters begin reporting on an earthquake in Beijing at 4 a.m., at what time will viewers in New York see the coverage?

Step 1: Find Beijing’s time zone.
Beijing is in China → looks like UTC+8 on the map.

Step 2: Find New York’s time zone.
New York is on the East Coast of the U.S. → typically UTC-5 (Eastern Time). But wait — check the map.

Looking at the map: New York is near the -5 line? Actually, looking carefully — the eastern U.S. is marked as -5? Let me confirm.

Actually, standard time zones:
- Beijing: UTC+8
- New York: UTC-5 (during Standard Time; but since no date is given, we assume standard time unless specified otherwise — and April 13 might be during Daylight Saving, but the problem doesn’t mention DST, so we’ll go with standard offsets shown on map).

On the map, New York appears to be at UTC-5.

Time difference: From UTC+8 to UTC-5 → that’s 13 hours behind.

Because: 8 - (-5) = 13 hours difference.

So if it’s 4 a.m. in Beijing, subtract 13 hours to get New York time.

4 a.m. minus 13 hours:

Think backwards:
4 a.m. minus 4 hours = midnight (12 a.m.)
Still need to subtract 9 more hours → go back into previous day.

Midnight minus 9 hours = 3 p.m. the previous day.

So: 4 a.m. Beijing time = 3 p.m. (previous day) in New York.

But let’s do it numerically:

4:00 a.m. = 04:00
04:00 - 13 hours = ?

04:00 - 13 = -9 → which means 24 - 9 = 15:00 → 3 p.m. the day before.

Yes.

✔ So viewers in New York would see it at 3 p.m. the previous day.

But wait — is this realistic? Earthquake happens at 4 a.m. Beijing time → news reports start then → broadcast live → so yes, New York sees it 13 hours earlier in their local time, meaning the prior afternoon.

Correct.

---

Question 3:
> The flight from Chicago to Moscow is 20 hours long. If a plane leaves Chicago at 6:30 p.m. on January 26th, what time and day will it arrive in Moscow?

Step 1: Find Chicago’s time zone.
Chicago is Central Time → UTC-6 (standard time). Map confirms — central U.S. is around -6.

Step 2: Find Moscow’s time zone.
Moscow is in Russia → typically UTC+3. On the map, Moscow is near +3 or +4? Let’s check.

Looking at the map: Moscow is east of Europe — likely UTC+3 or +4. Standard time for Moscow is UTC+3 (though sometimes they change, but again, no DST mentioned, so use standard).

Assume Moscow is UTC+3.

Time difference: From UTC-6 to UTC+3 → that’s 9 hours ahead.

Because: 3 - (-6) = 9 hours.

So when it’s 6:30 p.m. in Chicago, it’s already 6:30 p.m. + 9 hours = 3:30 a.m. next day in Moscow.

But the flight takes 20 hours — so we add 20 hours to departure time in Chicago, THEN convert to Moscow time? Or better: convert departure time to Moscow time first, then add flight duration.

Better approach:

Departure: Chicago, Jan 26, 6:30 p.m. (UTC-6)

Convert to UTC: Add 6 hours → 6:30 p.m. + 6h = 12:30 a.m. on Jan 27 (UTC)

Now, Moscow is UTC+3 → so add 3 hours to UTC to get Moscow time.

But actually, since flight duration is fixed, easiest way:

Total elapsed time: 20 hours.

Departure in Chicago local time: Jan 26, 18:30

Add 20 hours: 18:30 + 20:00 = 38:30 → which is 14:30 (2:30 p.m.) on Jan 27 (since 38:30 - 24:00 = 14:30 next day)

BUT — that’s still Chicago time! We need arrival time in Moscow local time.

Since Moscow is 9 hours ahead of Chicago, when it’s 2:30 p.m. on Jan 27 in Chicago, it’s 2:30 p.m. + 9 hours = 11:30 p.m. on Jan 27 in Moscow.

Wait — let’s verify:

Alternative method:

Convert departure time to Moscow time first.

Chicago: Jan 26, 6:30 p.m. (UTC-6)

Moscow is UTC+3 → difference is +9 hours.

So departure time in Moscow time: Jan 26, 6:30 p.m. + 9h = Jan 27, 3:30 a.m.

Flight duration: 20 hours.

Arrival in Moscow time: Jan 27, 3:30 a.m. + 20 hours = Jan 27, 23:30 → 11:30 p.m. on Jan 27.

Same answer.

✔ So arrival is 11:30 p.m. on January 27 in Moscow.

But wait — is Moscow really UTC+3? In some years, Russia has changed time zones. However, based on typical educational maps and the context, UTC+3 is correct for Moscow.

Also, note: January is winter, so no daylight saving issues.

Final confirmation:

Departure: Chicago, Jan 26, 18:30 CST (UTC-6)

In UTC: 18:30 + 6 = 00:30 Jan 27 UTC

Flight 20 hours → arrives at 20:30 UTC on Jan 27

Moscow is UTC+3 → 20:30 + 3 = 23:30 → 11:30 p.m. Jan 27

Perfect.

---

Now, compiling answers:

1. California: 11 a.m. (same day)
2. New York: 3 p.m. the previous day
3. Moscow: 11:30 p.m. on January 27

But let’s write them clearly as requested.

──────────────────────────────────────

Final Answer:
1. 11 a.m.
2. 3 p.m. the previous day
3. 11:30 p.m. on January 27