Tip: The share link stores your timers in the URL. Anyone you share it with will see the same list.
Upcoming
All timers
#
Event
Target (local to event)
UTC
Time left
Business days
ICS
Remove
Optional ad slot
Quick start
Enter an Event name and pick its time zone (IANA format like America/New_York).
Choose the Date and Time (local to that time zone).
Set Repeat (none/daily/weekly/monthly/yearly) and whether to count up after zero.
Click Add event. Timers update live and stay in the URL for easy sharing.
What this calculator assumes
Time zones: Uses the browser’s IANA time-zone database. City nicknames (e.g., “New York”) are mapped to the official zone.
DST handling: Ambiguous/skipped clocks on DST change days are resolved using time-zone rules.
Business days: Excludes Saturdays and Sundays only (no regional holidays).
Share link: Timers are encoded in the URL—anyone with the link sees the same list.
Results explained
Upcoming: Your next event, shown in its local time with a live countdown.
All timers: Each event shows local target time, UTC time, Time left, Business days, and a one-click .ics file.
.ics file: Downloads a calendar event for the next occurrence (1-hour default). Repeating events set an RRULE.
FAQ
What time zone format should I use?
Use IANA names like America/Chicago or Europe/London. Common city shortcuts are auto-mapped.
Why is the time I entered shifting by an hour?
Likely a DST edge case. The app converts wall time to UTC using the zone’s rules. On DST change dates, some local times are ambiguous or skipped; the code resolves this consistently.
Does “Business days” include holidays?
No—only Monday–Friday are counted. Holidays aren’t considered.
What does “Count up” do?
After the target passes, the timer shows elapsed time (e.g., +2d 03h) instead of stopping at zero.
How do repeats work?
Daily/weekly add fixed days; monthly/yearly rebuild the same local date/time in the event’s zone and adjust for month length and DST.
Is the share link private?
It’s just a URL. Anyone with it can view your timers. Don’t share sensitive event names.