Time difference between Rio de Mouro and London
London and Rio de Mouro are on the same clock.
Local time in both cities
Rio de Mouro · Portugal
04:45
London · United Kingdom
04:45
London and Rio de Mouro are on the same clock.
same day
Time zones
| Rio de Mouro | Europe/Lisbon · UTC+01:00 |
|---|---|
| London | Europe/London · UTC+01:00 |
Rio de Mouro is currently on daylight saving time (UTC+01:00). Next change: 2026-10-25 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-21 local time in Rio de Mouro. The two places start and end daylight saving on different dates, so another day can give a different result.
| Rio de Mouro (source) | London (target) |
|---|---|
| 00:00 | 00:00 |
| 01:00 | 01:00 |
| 02:00 | 02:00 |
| 03:00 | 03:00 |
| 04:00 | 04:00 |
| 05:00 | 05:00 |
| 06:00 | 06:00 |
| 07:00 | 07:00 |
| 08:00 | 08:00 |
| 09:00 | 09:00 |
| 10:00 | 10:00 |
| 11:00 | 11:00 |
| 12:00 | 12:00 |
| 13:00 | 13:00 |
| 14:00 | 14:00 |
| 15:00 | 15:00 |
| 16:00 | 16:00 |
| 17:00 | 17:00 |
| 18:00 | 18:00 |
| 19:00 | 19:00 |
| 20:00 | 20:00 |
| 21:00 | 21:00 |
| 22:00 | 22:00 |
| 23:00 | 23:00 |
Other common differences from Rio de Mouro
FAQ
- How many hours apart are Rio de Mouro 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. Rio de Mouro uses Europe/Lisbon 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 Rio de Mouro; 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.