Clock changes in Riga
Latvia Europe/Riga Daylight saving time
Standard time
UTC+2
EET
Daylight saving time
UTC+3
EEST
Next change
October 25, 2026
Back 60 min
Most recent change
March 29, 2026
Forward 60 min
Upcoming changes (2026–2035)
| Local date | Direction | Clocks go | Offset after | Then called | UTC instant |
|---|---|---|---|---|---|
| March 29, 2026 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST (DST) | |
| October 25, 2026 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET (standard) | |
| March 28, 2027 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST (DST) | |
| October 31, 2027 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET (standard) | |
| March 26, 2028 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST (DST) | |
| October 29, 2028 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET (standard) | |
| March 25, 2029 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST (DST) | |
| October 28, 2029 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET (standard) | |
| March 31, 2030 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST (DST) | |
| October 27, 2030 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET (standard) | |
| March 30, 2031 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST (DST) | |
| October 26, 2031 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET (standard) | |
| March 28, 2032 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST (DST) | |
| October 31, 2032 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET (standard) | |
| March 27, 2033 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST (DST) | |
| October 30, 2033 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET (standard) | |
| March 26, 2034 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST (DST) | |
| October 29, 2034 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET (standard) | |
| March 25, 2035 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST (DST) | |
| October 28, 2035 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET (standard) |
Daylight saving period by year
| Year | DST starts | DST ends | Changes |
|---|---|---|---|
| 2026 | March 29 at 04:00 | October 25 at 03:00 | 2 |
| 2027 | March 28 at 04:00 | October 31 at 03:00 | 2 |
| 2028 | March 26 at 04:00 | October 29 at 03:00 | 2 |
| 2029 | March 25 at 04:00 | October 28 at 03:00 | 2 |
| 2030 | March 31 at 04:00 | October 27 at 03:00 | 2 |
| 2031 | March 30 at 04:00 | October 26 at 03:00 | 2 |
| 2032 | March 28 at 04:00 | October 31 at 03:00 | 2 |
| 2033 | March 27 at 04:00 | October 30 at 03:00 | 2 |
| 2034 | March 26 at 04:00 | October 29 at 03:00 | 2 |
| 2035 | March 25 at 04:00 | October 28 at 03:00 | 2 |
Past changes (2016–2025)
Most recent first. Useful when checking what a timestamp meant at the time it was recorded.
| Local date | Change | Clocks went | Offset after | Then called |
|---|---|---|---|---|
| October 26, 2025 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET |
| March 30, 2025 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST |
| October 27, 2024 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET |
| March 31, 2024 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST |
| October 29, 2023 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET |
| March 26, 2023 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST |
| October 30, 2022 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET |
| March 27, 2022 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST |
| October 31, 2021 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET |
| March 28, 2021 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST |
| October 25, 2020 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET |
| March 29, 2020 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST |
| October 27, 2019 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET |
| March 31, 2019 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST |
| October 28, 2018 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET |
| March 25, 2018 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST |
| October 29, 2017 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET |
| March 26, 2017 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST |
| October 30, 2016 | Back 60 min | 03:59 → 03:00 | UTC+02:00 | EET |
| March 27, 2016 | Forward 60 min | 02:59 → 04:00 | UTC+03:00 | EEST |
Why this matters for stored times
A clock change is the reason a future appointment should never be stored as an offset. Save
"2027-03-14 09:00 at Europe/Riga" and it resolves correctly whatever the rules
turn out to be. Save "2027-03-14 09:00 UTC+03:00" and you have
frozen today's rules into a date that may fall on the other side of a transition — or of a
change to the rules themselves.
Frequently asked questions
Does Riga change its clocks?
Yes. Riga observes daylight saving time, moving between UTC+2 (EET) and UTC+3 (EEST). Under the rules currently published, the next 10 years contain 20 changes, all listed on this page.
When do the clocks next change in Riga?
March 29, 2026 — clocks go forward 1 hour, from 03:00 EET to 04:00 EEST. Because the change is defined in Riga's own local time, it happens at that reading regardless of what other countries are doing that weekend.
What happens to the hour that is skipped or repeated?
When the clocks go forward, the local times inside the gap never occur — so a meeting set for one of them has no instant to happen at. When they go back, the hour before the change repeats, so that local reading occurs twice, an hour apart. Our time zone converter flags both cases instead of silently picking one.
How far ahead can these dates be trusted?
They come from the IANA time zone database, which is what browsers and operating systems use, and they reflect the rules published today. Governments occasionally change or abolish daylight saving with only weeks of notice; when that happens the database is updated and this page is regenerated from it on the next build.