It is 1:46 pm in Europe/Riga
Europe/Riga is the IANA identifier for the time zone of Riga in Latvia. It is running at UTC+3 right now, abbreviated EEST, and the local date is Friday, September 25, 2026. The zone is on its summer offset at the moment.
What time is it in Europe/Riga right now
1:46 pm on Friday, September 25, 2026, as this page was served, which in 24 hour form is 13:46. The clock above ticks on from there in your own browser. The offset is a whole 3 hours ahead of UTC, so a UTC timestamp converts here by changing the hour and leaving the minutes exactly as they are.
41 other zones read UTC+3 at this instant. They are interchangeable as a clock reading today and not as an identifier: storing UTC+3 instead of Europe/Riga throws away the rule that decides what they all do at the next transition.
The UTC offset of Europe/Riga
An offset of UTC+3 names the meridian 45.0 degrees east. Riga, Latvia actually sits at 24.11 degrees east, which is 20.9 degrees west of it, so the sun there runs about 84 minutes behind the clock before daylight saving is even considered. Zone boundaries are drawn by borders and by convenience, not by longitude, and this is the size of the gap that produces.
Because this zone moves its clocks, UTC+3 is only today's answer. It runs at UTC+2 for the winter part of the year and UTC+3 for the summer part, a difference of 1 hour, and any gap memorised against it is wrong for part of the year.
Daylight saving in Europe/Riga
Europe/Riga does observe daylight saving. The next change is on October 25, 2026: at 3:00 am local the clocks go back, and UTC+3 becomes UTC+2. That hour is repeated, so every reading inside it happens twice, which is why a wall clock time in this zone is not always a single instant.
Every clock change the database has for this zone in 2025, 2026 and 2027, with the exact local reading either side of the jump.
| Date | Clock before | Clock after | Change | Status |
|---|---|---|---|---|
| March 30, 2025 | 2:59 am | 4:00 am | forward an hour, UTC+2 to UTC+3 | already happened |
| October 26, 2025 | 3:59 am | 3:00 am | back an hour, UTC+3 to UTC+2 | already happened |
| March 29, 2026 | 2:59 am | 4:00 am | forward an hour, UTC+2 to UTC+3 | already happened |
| October 25, 2026 | 3:59 am | 3:00 am | back an hour, UTC+3 to UTC+2 | still to come |
| March 28, 2027 | 2:59 am | 4:00 am | forward an hour, UTC+2 to UTC+3 | still to come |
| October 31, 2027 | 3:59 am | 3:00 am | back an hour, UTC+3 to UTC+2 | still to come |
How the offset of Europe/Riga has changed since 1970
Read on 1 January and 1 July of each year, which is the cheapest pair of samples that shows both the winter offset and whether the clocks moved that summer. The zone has passed through 6 distinct eras in that time and has used 3 different offsets: UTC+2, UTC+3, UTC+4. Its current behaviour has held since 2001. A rule change that began and ended between July and the following January is invisible to this sampling, so the table is a shape rather than a complete edit history.
| Years | 1 January | 1 July | Behaviour |
|---|---|---|---|
| 1970 to 1980 | UTC+3 | UTC+3 | one offset all year |
| 1981 to 1988 | UTC+3 | UTC+4 | clocks moved, 1 hour apart |
| 1989 | UTC+3 | UTC+3 | one offset all year |
| 1990 to 1999 | UTC+2 | UTC+3 | clocks moved, 1 hour apart |
| 2000 | UTC+2 | UTC+2 | one offset all year |
| 2001 to 2026 | UTC+2 | UTC+3 | clocks moved, 1 hour apart |
The earliest summer shift this sampling sees here is 1981, and the zone has kept moving its clocks since. The dates the change falls on have moved several times even where the rule has not.
Countries and regions that use Europe/Riga
One country uses Europe/Riga: Latvia, which keeps this as its only time zone and has a population of about 1,880,000.
Cities in the Europe/Riga time zone
The one city this site covers inside Europe/Riga, each with a live clock and today's sunrise and sunset worked out from its own coordinate. The clock reading is a property of the identifier, so it is the same anywhere else in the zone; the sunrise is not, because that is set by latitude and longitude.
| City | Where | Time now | Sunrise | Sunset | Daylight |
|---|---|---|---|---|---|
| Riga | Latvia | 1:46 pm | 7:14 am | 7:15 pm | 12h 00m |
The sun against the clock in Europe/Riga
Worked out for Riga, Latvia, the city this site covers inside the zone, at 56.95 degrees north, 24.11 degrees east. The sun rises at 7:14 am and sets at 7:15 pm, giving 12 hours of daylight. Solar noon, the moment the sun is highest, falls at 1:15 pm, which is 75 minutes after clock noon.
That gap is the whole argument about where zone lines belong, in one number. It is made of three things: Riga, Latvia sitting 20.9 degrees west of the UTC+3 meridian, the equation of time, which today runs 8.3 minutes ahead of mean time, and the hour of daylight saving currently in force. Full sunrise and sunset times for Riga.
Convert Europe/Riga to another time zone
The converter is keyed on the abbreviations people type rather than on identifiers. Europe/Riga is at UTC+3 right now, the same reading as EET, so these pages answer the same question for it today. They will diverge if the two zones ever adopt different daylight saving rules, which is exactly why the identifier is the thing worth storing.
Questions about Europe/Riga
- What time is it in Europe/Riga right now?
- 1:46 pm on Friday, September 25, 2026, as this page was served. The clock at the top of the page ticks on from there.
- What is the UTC offset of Europe/Riga?
- UTC+3 at this instant, and it alternates between UTC+2 in winter and UTC+3 in summer.
- Does Europe/Riga observe daylight saving time?
- Yes. The next change is October 25, 2026, when the clocks go back.
- What is the abbreviation for Europe/Riga?
- EEST at this instant. The letters change with the season, because the standard and summer offsets have separate names.
- Which countries use Europe/Riga?
- Latvia.
- Why store Europe/Riga instead of UTC+3?
- Because the offset is an output and the identifier is the input. This zone alone has two offsets in a year, and 41 other zones share its current reading while carrying different rules. A record storing UTC+3 cannot tell them apart; a record storing
Europe/Rigakeeps working through every future rule change.