Time difference between Tokyo and Robāţ Karīm
Robāţ Karīm is 5 hours 30 minutes behind Tokyo.
Local time in both cities
Tokyo · Japan
00:28
JapanRobāţ Karīm · Iran
18:58
IranRobāţ Karīm is 5 hours 30 minutes behind Tokyo.
still the previous day
Time zones
| Tokyo | Asia/Tokyo · UTC+09:00 |
|---|---|
| Robāţ Karīm | Asia/Tehran · UTC+03:30 |
Tokyo does not observe daylight saving and stays on UTC+09:00 all year.
Robāţ Karīm does not observe daylight saving and stays on UTC+03:30 all year.
Hour-by-hour conversion
Calculated for 2026-09-22 local time in Tokyo. The two places start and end daylight saving on different dates, so another day can give a different result.
| Tokyo (source) | Robāţ Karīm (target) |
|---|---|
| 00:00 | 18:30 prev day |
| 01:00 | 19:30 prev day |
| 02:00 | 20:30 prev day |
| 03:00 | 21:30 prev day |
| 04:00 | 22:30 prev day |
| 05:00 | 23:30 prev day |
| 06:00 | 00:30 |
| 07:00 | 01:30 |
| 08:00 | 02:30 |
| 09:00 | 03:30 |
| 10:00 | 04:30 |
| 11:00 | 05:30 |
| 12:00 | 06:30 |
| 13:00 | 07:30 |
| 14:00 | 08:30 |
| 15:00 | 09:30 |
| 16:00 | 10:30 |
| 17:00 | 11:30 |
| 18:00 | 12:30 |
| 19:00 | 13:30 |
| 20:00 | 14:30 |
| 21:00 | 15:30 |
| 22:00 | 16:30 |
| 23:00 | 17:30 |
Other common differences from Tokyo
FAQ
- How many hours apart are Tokyo and Robāţ Karīm 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. Tokyo uses Asia/Tokyo and Robāţ Karīm uses Asia/Tehran; 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 Tokyo; the right column is the local time in Robāţ Karīm 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.