Time duration calculator

Measure an unzoned date-and-time interval

Use this page when you want the arithmetic interval between two calendar date-and-time values. The tool treats each day as 24 hours and each hour as 60 minutes. It reports decimal hours, total minutes, and a days/hours/minutes breakdown. The inputs have minute precision, so seconds are not included.

These values have no location attached. This is appropriate for a simple timetable model, but it is different from measuring real elapsed time across a daylight-saving change. If location-specific offsets matter, resolve the endpoints to UTC first with time-zone information.

Break down a multi-day interval

From October 20, 2026 at 09:00 to October 22 at 17:30 is two complete 24-hour days plus eight hours and 30 minutes. Total duration is 56.5 hours or 3,390 minutes. The breakdown is derived from the same minute difference, so its parts reconcile exactly.

An equal start and end returns zero. An end before the start is reported as invalid instead of silently taking an absolute value, since an accidental reversed interval can conceal a scheduling error. Breaks are not subtracted on this page. For a single shift with an unpaid break, use the hours calculator.

Frequently asked questions

Is 1.5 days the same as one day and five hours?

No. Half a day is 12 hours, so 1.5 days is 36 hours.

Are leap seconds included?

No. This is calendar-and-clock arithmetic at minute precision.

Can I subtract breaks?

Use Hours for a single shift, or subtract a separately verified break duration from the total.

Calendar dates and clock time are different

A calendar date identifies a day, while a timestamp identifies an instant. For date-only arithmetic, this toolkit works with Gregorian dates and a consistent UTC representation internally. That prevents your device's local daylight-saving transition from turning a one-day calendar difference into 23 or 25 hours. It does not mean your appointment happens at midnight UTC; it is simply a way to compare dates without a hidden local-clock adjustment.

Enter four-digit years and check the month and day. The supported input range is 1900 through 2100. The Gregorian leap-year rule adds February 29 in years divisible by four, except century years that are not divisible by 400. Thus 2000 is a leap year and 1900 is not. Invalid dates are reported instead of silently rolling into the next month.

The browser may display a date field in your device's preferred style. Written examples and results use year-month-day to remove ambiguity between month-first and day-first conventions. The ISO date and time overview explains the purpose of this international date notation. Always copy the year as well as the month and day when sharing an estimate.

An inclusive count answers how many named dates belong to a range; an elapsed difference answers how many date boundaries separate them. Monday to Tuesday is one elapsed day but two dates when both endpoints count. Decide which question your task asks before interpreting the result. A billing period, reservation, classroom schedule, and contract deadline may use different endpoint conventions.

Date-only tools do not apply a country's holiday calendar, historical calendar reforms, legal deadline extensions, or payroll rules. Work-day exceptions must be entered explicitly. Time-zone conversion is a separate calculation because the offset depends on place and date. If an event crosses a clock change, use dated time-zone information when you need actual elapsed time.

For important deadlines, confirm the relevant organization's calendar, time zone, and cutoff time. A date count does not establish whether an office is open or whether a submission is on time. Keep a record of the chosen endpoints and exclusions so another person can reproduce the count.

Using and checking the result

All inputs and arithmetic on this page stay in the current browser. Switching between English and Chinese keeps the current form values in memory during navigation. Reloading the site restores the example. The toolkit does not save calculation inputs in cookies or browser storage, and the usage event records only that a calculation was completed, not the values or answer.

The initial values are a worked example, not a suggestion about your personal situation. Replace every relevant field before using the answer. Editing a field clears the previous result so it is not mistaken for a calculation using the new values. Use Reset example to return to the starting illustration.

If a result appears unexpected, repeat a small example by hand. Check units, signs, endpoints, and whether a percentage was entered as 30 rather than 0.30. To report an issue, use the contact form with non-sensitive sample inputs, the answer you expected, and the steps that produced the difference. Do not include private academic records or identifying details.

Verify a schedule before you copy the answer

A short independent check is often enough to catch a date-entry mistake. Move one endpoint by exactly seven days and observe what changes. A simple calendar difference should change by seven. A weekday should remain the same. A fixed five-day working week generally adds five eligible days over a complete additional week, but entered holidays can reduce that increment. The expected behavior depends on the selected tool, so compare the question as well as the number.

Check the year whenever a result appears unexpectedly large. Two matching month-and-day values in adjacent years are about a year apart, not zero days apart. Conversely, a date-and-time interval can cross midnight with only a few minutes elapsed. A visible date change alone does not tell you whether you are counting days, hours, or an inclusive list of dates.

For a schedule that spans February or the end of a month, test one neighboring date. February 28 to March 1 depends on whether that year has February 29. January 31 plus thirty days is a day-count operation, while moving to the same day next month requires a month-end convention. Write that convention down when sharing a plan with another person.

The reference date in the form is part of the input, not a hidden promise to follow the current day. An example remains an example until you replace it. If you return tomorrow, review the reference date before interpreting a birthday or age result. A stored screenshot or copied answer should include the reference date so its meaning stays clear later.

For deadlines that involve an organization, also record the location and cutoff time separately. A calendar calculation can be arithmetically correct while a submission still falls outside opening hours or a local deadline. Confirm exceptions from the organization rather than inferring them from a weekday label.