Time Duration Calculator

Calculate overnight clock intervals or elapsed minutes using explicit UTC offsets.

Find hours and minutes between two clock times, or compare two dated instants using their explicit UTC offsets. Choose the next-day option yourself for an overnight clock interval.

Calculations stay in this browser without uploading or saving inputs. Editing any input clears the earlier result and download. Decimal hours are rounded to six places; whole-minute totals are the exact output.

This tool runs entirely in your browser. Your data is never uploaded, never stored, and never leaves your device.

Calculate a same-day/overnight clock interval or elapsed minutes between dated instants with explicit UTC offsets.

How to use it

1Choose wall-clock times or dated instants with explicit offsets.
2Enter both endpoints; mark the end as next day only when intended in clock mode.
3Review whole minutes, seconds, hours:minutes and rounded decimal hours.
4Download the active-input JSON record; edits remove earlier output.

Example

Input: 22:45 → 06:15, with End is next day selected.
Output: 450 minutes; 7:30; 7.5 decimal hours; 27,000 seconds.

Clock arithmetic does not look up DST. Explicit-offset mode requires the correct offset at each endpoint.

What happens to your data

Inputs are processed locally without uploads or persistence. The optional JSON download contains active endpoints and the calculation basis.

Last updated October 2026

Two clock readings are not always enough to identify elapsed time. An overnight interval needs a day boundary, and a repeated local hour needs an offset to identify which instant it represents. This time duration calculator separates those questions into clock mode and dated-instant mode. Clock mode counts hours and minutes with an explicit next-day option. Dated-instant mode converts each endpoint from its entered numeric UTC offset before subtracting.

The result includes total whole minutes, seconds, hours:minutes, a 24-hour-day breakdown and decimal hours. Download a local JSON record showing the active inputs and calculation basis. No city, local computer timezone or daylight-saving rule is guessed.

How it works

Clock mode converts each 24-hour HH:MM input into minutes after midnight. Duration = end minutes − start minutes, plus 1,440 only when End is next day is selected. An earlier end without that selection produces an error instead of silently assuming overnight. Equal times are zero on the same day or 24 hours on the next day. The next-day option always advances the end's calendar day, so an interval can exceed 24 hours and reach 47 hours 59 minutes.

For dated instants, enter YYYY-MM-DDTHH:MM and a known UTC offset for each endpoint. UTC = local date-time − offset. Thus 01:30 at -04:00 and 01:30 at -05:00 are one hour apart even though the clock readings match. An offset is not a named timezone or a rule for future dates: the tool does not know whether a location actually used that offset on the selected day. Check each endpoint's applicable offset yourself.

Gregorian dates are checked explicitly, including leap days and years below 0100, rather than relying on a parser that may reinterpret a short year. Years 0001–9999 and known offsets from -14:00 through +14:00 are supported; conversion must keep the UTC result within that year range. Z and +00:00 mean UTC. The unknown-offset spelling -00:00 is rejected. Inputs have minute precision; seconds and leap-second notation are outside this workflow.

Whole-minute differences use integer arithmetic. Total seconds are minutes × 60. The day breakdown uses fixed 24-hour days, not a calendar-month/year decomposition. Decimal hours divide minutes by 60 and round to six decimal places; use the integer-minute field when an exact downstream total matters. An end instant before its start is rejected rather than returning an unexplained absolute value.

Clock mode deliberately performs wall-clock arithmetic, so it cannot infer a daylight-saving clock change. Dated-instant mode can represent different endpoint offsets, but does not look up IANA zone transitions or validate a city. This is useful for explicit-offset logs, travel records and timestamps where the offset is known. It does not replace a timezone database, payroll policy or a legal timekeeping system.

All calculations run in the browser. The JSON records only active-mode inputs; an inactive offset or next-day flag is not silently used. Changing the basis clears the endpoint fields, and any edit removes the old result and download so an earlier interval is not mistaken for the current one.

Worked example: An explicitly overnight clock interval

Input: Start 22:45; end 06:15; End is next day selected.
Result: 7:30 hours:minutes; 450 minutes; 27,000 seconds; 7.5 decimal hours.

This is wall-clock arithmetic. Use explicit-offset dated instants when known offset differences matter.

Common use cases

Calculate a 22:45 to 06:15 overnight interval with an explicit next-day end.
Compare two dated log timestamps whose numeric UTC offsets differ.
Obtain whole-minute totals and decimal hours without confusing 7:30 with 7.30 hours.
Save a private local calculation record with its endpoint assumptions.

Frequently asked questions

How do I calculate hours between two times overnight?＋

Enter both 24-hour clock readings and select End is next day. For 22:45 to 06:15, the result is 450 minutes or 7 hours 30 minutes. The tool does not assume overnight automatically, and clock mode does not adjust for daylight-saving changes.

Is 7 hours 30 minutes the same as 7.30 decimal hours?＋

No. Thirty minutes is half an hour, so 7 hours 30 minutes equals 7.5 decimal hours. The output labels hours:minutes and decimal hours separately, with whole minutes available for exact calculations.

Does it handle daylight-saving changes?＋

Clock mode does not. Dated-instant mode uses the UTC offset entered for each endpoint, so it can represent a change when the correct offsets are supplied. It does not choose offsets from city names or validate daylight-saving rules automatically.

Why do identical local times sometimes produce one hour?＋

Explicit offsets identify different instants. For example, 2026-11-01T01:30 at -04:00 is 05:30 UTC, while the same date-time at -05:00 is 06:30 UTC. Their elapsed difference is 60 minutes. This example illustrates offset arithmetic, not a claim about every city's rules.

Are seconds, leap seconds or calendar months included?＋

Inputs use whole-minute precision and do not accept leap-second notation. Total seconds are derived from the minute total. The day breakdown means 24-hour periods; the tool does not express a result as variable-length calendar months or years.

Are my timestamps uploaded?＋

No input is uploaded or saved by the calculator. The optional JSON download includes active inputs and the calculation basis on your device. An edit clears the old result.