Time difference between Paris and Río Tercero
Río Tercero is 5 hours behind Paris.
Local time in both cities
Paris · France
15:21
Río Tercero · Argentina
10:21
Río Tercero is 5 hours behind Paris.
same day
Time zones
| Paris | Europe/Paris · UTC+02:00 |
|---|---|
| Río Tercero | America/Argentina/Cordoba · UTC-03:00 |
Paris is currently on daylight saving time (UTC+02:00). Next change: 2026-10-25 02:00.
Río Tercero does not observe daylight saving and stays on UTC-03:00 all year.
Hour-by-hour conversion
Calculated for 2026-09-21 local time in Paris. The two places start and end daylight saving on different dates, so another day can give a different result.
| Paris (source) | Río Tercero (target) |
|---|---|
| 00:00 | 19:00 prev day |
| 01:00 | 20:00 prev day |
| 02:00 | 21:00 prev day |
| 03:00 | 22:00 prev day |
| 04:00 | 23:00 prev day |
| 05:00 | 00:00 |
| 06:00 | 01:00 |
| 07:00 | 02:00 |
| 08:00 | 03:00 |
| 09:00 | 04:00 |
| 10:00 | 05:00 |
| 11:00 | 06:00 |
| 12:00 | 07:00 |
| 13:00 | 08:00 |
| 14:00 | 09:00 |
| 15:00 | 10:00 |
| 16:00 | 11:00 |
| 17:00 | 12:00 |
| 18:00 | 13:00 |
| 19:00 | 14:00 |
| 20:00 | 15:00 |
| 21:00 | 16:00 |
| 22:00 | 17:00 |
| 23:00 | 18:00 |
Other common differences from Paris
FAQ
- How many hours apart are Paris and Río Tercero 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. Paris uses Europe/Paris and Río Tercero uses America/Argentina/Cordoba; 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 Paris; the right column is the local time in Río Tercero 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.