Time difference between Cockburn Town and London

London is 5 hours ahead of Cockburn Town.

America/Grand_Turk Europe/London same day

Local time in both cities

Cockburn Town · Turks and Caicos Islands
18:21
Sunday, 20 September 2026
America/Grand_Turk · UTC-04:00
London · United Kingdom
23:21
Sunday, 20 September 2026
Europe/London · UTC+01:00

London is 5 hours ahead of Cockburn Town.

same day

Time zones

Cockburn TownAmerica/Grand_Turk · UTC-04:00
LondonEurope/London · UTC+01:00

Cockburn Town is currently on daylight saving time (UTC-04:00). Next change: 2026-11-01 01:00.

London is currently on daylight saving time (UTC+01:00). Next change: 2026-10-25 01:00.

Hour-by-hour conversion

Calculated for 2026-09-20 local time in Cockburn Town. The two places start and end daylight saving on different dates, so another day can give a different result.

Cockburn Town (source) London (target)
00:00 05:00
01:00 06:00
02:00 07:00
03:00 08:00
04:00 09:00
05:00 10:00
06:00 11:00
07:00 12:00
08:00 13:00
09:00 14:00
10:00 15:00
11:00 16:00
12:00 17:00
13:00 18:00
14:00 19:00
15:00 20:00
16:00 21:00
17:00 22:00
18:00 23:00
19:00 00:00 next day
20:00 01:00 next day
21:00 02:00 next day
22:00 03:00 next day
23:00 04:00 next day

FAQ

How many hours apart are Cockburn Town and London right now?
The answer at the top of the page is calculated for the current moment and states which side is ahead. The gap changes during the year, because the two places usually start and end daylight saving on different dates.
Is this difference the same all year?
Not necessarily. Cockburn Town uses America/Grand_Turk and London uses Europe/London; if either observes daylight saving, the gap shifts during the year. Use “Convert a specific date and time” below to calculate it for a given day.
How do I read the conversion table?
The left column lists each whole hour in Cockburn Town; the right column is the local time in London at that same instant, with date rollovers marked. On the day clocks jump forward, some hours do not exist locally — the table says so instead of showing a plausible but wrong value.

Both cities