Time difference between Vasco da Gama and Tokyo
Tokyo is 3 hours 30 minutes ahead of Vasco da Gama.
Local time in both cities
Vasco da Gama · India
02:47
IndiaTokyo · Japan
06:17
JapanTokyo is 3 hours 30 minutes ahead of Vasco da Gama.
same day
Time zones
| Vasco da Gama | Asia/Kolkata · UTC+05:30 |
|---|---|
| Tokyo | Asia/Tokyo · UTC+09:00 |
Vasco da Gama does not observe daylight saving and stays on UTC+05:30 all year.
Tokyo does not observe daylight saving and stays on UTC+09:00 all year.
Hour-by-hour conversion
Calculated for 2026-09-22 local time in Vasco da Gama. The two places start and end daylight saving on different dates, so another day can give a different result.
| Vasco da Gama (source) | Tokyo (target) |
|---|---|
| 00:00 | 03:30 |
| 01:00 | 04:30 |
| 02:00 | 05:30 |
| 03:00 | 06:30 |
| 04:00 | 07:30 |
| 05:00 | 08:30 |
| 06:00 | 09:30 |
| 07:00 | 10:30 |
| 08:00 | 11:30 |
| 09:00 | 12:30 |
| 10:00 | 13:30 |
| 11:00 | 14:30 |
| 12:00 | 15:30 |
| 13:00 | 16:30 |
| 14:00 | 17:30 |
| 15:00 | 18:30 |
| 16:00 | 19:30 |
| 17:00 | 20:30 |
| 18:00 | 21:30 |
| 19:00 | 22:30 |
| 20:00 | 23:30 |
| 21:00 | 00:30 next day |
| 22:00 | 01:30 next day |
| 23:00 | 02:30 next day |
Other common differences from Vasco da Gama
FAQ
- How many hours apart are Vasco da Gama and Tokyo 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. Vasco da Gama uses Asia/Kolkata and Tokyo uses Asia/Tokyo; 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 Vasco da Gama; the right column is the local time in Tokyo 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.