Time difference between Eloy Alfaro and Tokyo

Tokyo is 14 hours ahead of Eloy Alfaro.

America/Guayaquil Asia/Tokyo already the next day

Local time in both cities

Eloy Alfaro · Ecuador
18:46
Sunday, 20 September 2026
America/Guayaquil · UTC-05:00
Tokyo · Japan
08:46
Monday, 21 September 2026
Asia/Tokyo · UTC+09:00

Tokyo is 14 hours ahead of Eloy Alfaro.

already the next day

Time zones

Eloy AlfaroAmerica/Guayaquil · UTC-05:00
TokyoAsia/Tokyo · UTC+09:00

Eloy Alfaro does not observe daylight saving and stays on UTC-05:00 all year.

Tokyo does not observe daylight saving and stays on UTC+09:00 all year.

Hour-by-hour conversion

Calculated for 2026-09-20 local time in Eloy Alfaro. The two places start and end daylight saving on different dates, so another day can give a different result.

Eloy Alfaro (source) Tokyo (target)
00:00 14:00
01:00 15:00
02:00 16:00
03:00 17:00
04:00 18:00
05:00 19:00
06:00 20:00
07:00 21:00
08:00 22:00
09:00 23:00
10:00 00:00 next day
11:00 01:00 next day
12:00 02:00 next day
13:00 03:00 next day
14:00 04:00 next day
15:00 05:00 next day
16:00 06:00 next day
17:00 07:00 next day
18:00 08:00 next day
19:00 09:00 next day
20:00 10:00 next day
21:00 11:00 next day
22:00 12:00 next day
23:00 13:00 next day

FAQ

How many hours apart are Eloy Alfaro 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. Eloy Alfaro uses America/Guayaquil 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 Eloy Alfaro; 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.

Both cities