A repeated New York time
On November 1, 2026, 01:30 in America/New_York occurs twice. The first corresponds to 05:30 UTC and the second to 06:30 UTC. Choose the occurrence intended by the organizer.
Choose the local date and time of an event and specify the time zone where it happens. The tool resolves that wall-clock time to an instant and displays the elapsed days, hours, minutes, and seconds remaining.
Set a date, time, and time zone to display the countdown.
Days mean blocks of 24 elapsed hours. Spring clock-change gaps are rejected; repeated fall-back times let you choose the occurrence. This is a visual countdown with no alarm or notification.
Inputs and results are processed in this browser. This tool does not upload your entries or retain them after a page refresh.
Enter an event title, calendar date, 24-hour time, and IANA time-zone identifier.
If a clock change repeats the local time, choose the first or second occurrence.
Set the countdown. Copy or download the target information for an unambiguous record.
On November 1, 2026, 01:30 in America/New_York occurs twice. The first corresponds to 05:30 UTC and the second to 06:30 UTC. Choose the occurrence intended by the organizer.
March 8, 2026 at 02:30 in America/New_York falls in the spring clock-change gap. The tool rejects that local time rather than silently moving the event.
A date and time alone do not identify one worldwide instant. Region identifiers such as Europe/London include local offset rules. UTC is also available for events published in universal time.
Countdown days are blocks of 24 elapsed hours. They are not a count of calendar date boundaries. Around daylight saving changes, tomorrow at the same local clock time may be 23 or 25 elapsed hours away.
The countdown stops at zero and marks the target as reached. It does not continue as a negative timer, send a reminder, or create an external event. Editing any event field clears the active target until you set it again.
Yes. A valid past target immediately shows that the time has been reached.
No. Remaining time uses your device clock. An incorrect clock or later clock adjustment changes the displayed remaining time.
The calendar resolver accepts real dates from 1900 through 2100, using the time-zone rules provided by the browser.