Time difference between Três Lagoas and New York City

New York City and Três Lagoas are on the same clock.

America/Campo_Grande America/New_York same day

Local time in both cities

Três Lagoas · Brazil
16:34
Monday, 21 September 2026
America/Campo_Grande · UTC-04:00
New York City · United States
16:34
Monday, 21 September 2026
America/New_York · UTC-04:00

New York City and Três Lagoas are on the same clock.

same day

Time zones

Três LagoasAmerica/Campo_Grande · UTC-04:00
New York CityAmerica/New_York · UTC-04:00

Três Lagoas does not observe daylight saving and stays on UTC-04: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 Três Lagoas. The two places start and end daylight saving on different dates, so another day can give a different result.

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

FAQ

How many hours apart are Três Lagoas 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. Três Lagoas uses America/Campo_Grande 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 Três Lagoas; 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