Time difference between London and Indian Hills

Indian Hills is 8 hours behind London.

Europe/London America/Los_Angeles same day

Local time in both cities

London · United Kingdom
21:31
Sunday, 20 September 2026
Europe/London · UTC+01:00
Indian Hills · United States
13:31
Sunday, 20 September 2026
America/Los_Angeles · UTC-07:00

Indian Hills is 8 hours behind London.

same day

Time zones

LondonEurope/London · UTC+01:00
Indian HillsAmerica/Los_Angeles · UTC-07:00

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

Indian Hills is currently on daylight saving time (UTC-07:00). Next change: 2026-11-01 01:00.

Hour-by-hour conversion

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

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

FAQ

How many hours apart are London and Indian Hills 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. London uses Europe/London and Indian Hills uses America/Los_Angeles; 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 London; the right column is the local time in Indian Hills 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