Time difference between Idaho Falls and New York City

New York City is 2 hours ahead of Idaho Falls.

America/Boise America/New_York same day

Local time in both cities

Idaho Falls · United States
13:57
Monday, 21 September 2026
America/Boise · UTC-06:00
New York City · United States
15:57
Monday, 21 September 2026
America/New_York · UTC-04:00

New York City is 2 hours ahead of Idaho Falls.

same day

Time zones

Idaho FallsAmerica/Boise · UTC-06:00
New York CityAmerica/New_York · UTC-04:00

Idaho Falls is currently on daylight saving time (UTC-06:00). Next change: 2026-11-01 01:00.

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 Idaho Falls. The two places start and end daylight saving on different dates, so another day can give a different result.

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

FAQ

How many hours apart are Idaho Falls 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. Idaho Falls uses America/Boise 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 Idaho Falls; 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