Worked example. Change the dates to calculate your own.
30 minutes and 0 seconds remain. Both inputs use UTC.
- Total minutes
- 1590
- Time zone
- UTC
Treats both inputs as UTC moments and subtracts them. Does not interpret them in your browser's local zone. Reports full hours and the remaining minutes and seconds.
Dates stay in this page. No account, uploads or server calculation.
How this calculation works
The tool subtracts two UTC dates and times. It shows whole hours with remaining minutes and seconds. Both inputs use UTC, so local time zones and daylight-saving changes do not alter the calculation.
A worked example
October 1, 2026 at 09.00 UTC to October 2 at 11.30 UTC is 26 hours and 30 minutes. It is also 1,590 minutes. The same pair of clock labels in different local zones would not necessarily describe that duration.
Use UTC for both moments
The familiar date-and-time inputs do not convert from a city or the browser's zone. Both labels deliberately say UTC.
| UTC interval | Result |
|---|---|
| 09.00 to 09.00 on October 1, 2026 | 0 whole hours. |
| 09.00 to 10.30 on October 1, 2026 | 1 whole hour and 30 minutes. |
| October 1 at 09.00 to October 2 at 11.30, 2026 | 26 whole hours and 30 minutes. |
| An end before the start | Invalid order. |
Enter both times in UTC
Enter both dates and times in UTC, then Calculate. Convert local event times to UTC first. The tool does not infer a time zone from your location. The end must be on or after the start.
Keep your timed event in view
Add your event's actual local time and time zone in Daymark. Keep its countdown and preparation reminders together.
Get Daymark freeTwo active countdowns free. iOS 18 or iPadOS 18 or later. Apple Watch companion requires watchOS 11 or later.