Time difference between Tŭytepa and New York City

New York City is 9 hours behind Tŭytepa.

Asia/Tashkent America/New_York same day

Local time in both cities

Tŭytepa · Uzbekistan
16:50
Monday, 21 September 2026
Asia/Tashkent · UTC+05:00
New York City · United States
07:50
Monday, 21 September 2026
America/New_York · UTC-04:00

New York City is 9 hours behind Tŭytepa.

same day

Time zones

TŭytepaAsia/Tashkent · UTC+05:00
New York CityAmerica/New_York · UTC-04:00

Tŭytepa does not observe daylight saving and stays on UTC+05:00 all year.

New York City is currently on daylight saving time (UTC-04:00). Next change: 2026-11-01 01:00.

Hour-by-hour conversion

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

Tŭytepa (source) New York City (target)
00:00 15:00 prev day
01:00 16:00 prev day
02:00 17:00 prev day
03:00 18:00 prev day
04:00 19:00 prev day
05:00 20:00 prev day
06:00 21:00 prev day
07:00 22:00 prev day
08:00 23:00 prev day
09:00 00:00
10:00 01:00
11:00 02:00
12:00 03:00
13:00 04:00
14:00 05:00
15:00 06:00
16:00 07:00
17:00 08:00
18:00 09:00
19:00 10:00
20:00 11:00
21:00 12:00
22:00 13:00
23:00 14:00

FAQ

How many hours apart are Tŭytepa and New York City 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. Tŭytepa uses Asia/Tashkent and New York City uses America/New_York; 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 Tŭytepa; the right column is the local time in New York City 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