Duration Calculator

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from Duration Calculator

Duration Calculator helps you combine and compare duration entries. Durations are elapsed amounts of time rather than clock times; the tool parses supported notation and presents totals in several units. Time-related results are easiest to interpret when the input meaning is explicit: a calendar date, a local clock reading, an exact instant, and an elapsed duration are different kinds of information. Keep duration notation distinct from a time of day; 01:30 as a duration means elapsed time, not a zone-specific instant. Use the worked example to establish the expected behavior before entering a more complicated case. Months and years have variable calendar lengths, so a fixed-duration representation may not match adding a calendar month or year to a particular date. Keep the original date or duration alongside the result when sharing it, and include a time zone whenever the result refers to an actual moment. That context makes the result easier to check and prevents another reader from silently assuming a different clock or calendar convention.

Guide updated October 13, 2026

How to use this tool

1. Enter one duration per line, using an optional sign when adding or subtracting a line.
2. Use supported notation such as 1h, 30m, colon-separated time, or an ISO duration, then inspect line errors.
3. Review the result and its units or calendar labels. Keep duration notation distinct from a time of day; 01:30 as a duration means elapsed time, not a zone-specific instant.
4. Check the worked example or another simple known case before reusing the result in a schedule, calendar, or technical document.

SEE IT IN PRACTICE

A worked example

1h on one line; 30m on the next

1 hour 30 minutes; 5,400 seconds

One hour is 3,600 seconds and thirty minutes is 1,800 seconds, giving 5,400 seconds total.

Keep notation explicit when combining entries

Durations can be written with unit suffixes, colon-separated components, or decimal values. Those conventions are not interchangeable. Start with the tool’s supported forms and test a small total such as 1h plus 30m. Check the sign of entries used for subtraction and avoid assuming an unlabelled 30 means minutes. Retain the original entries when converting a timesheet or log.

Separate duration from calendar location

A duration describes how much time, not when an event happened. Adding that duration to a date introduces timezone and calendar questions that a pure sum does not answer. Fixed seconds and calendar months also have different meanings. Use seconds or another explicit fixed unit when exact elapsed time is required, and check whether any shorthand in the input is interpreted as a fixed or calendar-based quantity.

Colon notation and decimal hours

A colon-separated duration uses time components, while a decimal hour is a fraction of sixty minutes. For example, 1:30:00 and 1.5 hours describe the same interval, but 1.30 decimal hours describes 78 minutes. Keep the notation explicit when combining entries from different systems, and check any conversion before summing exported time records.

When this tool is useful

• Total recorded task durations with the relevant clock and calendar assumptions made explicit.
• Check a sum of time intervals using a simple, reproducible example.
• Convert duration units while keeping the original input available for comparison.

Tips for a better result

• Months and years have variable calendar lengths, so a fixed-duration representation may not match adding a calendar month or year to a particular date.
• Keep duration notation distinct from a time of day; 01:30 as a duration means elapsed time, not a zone-specific instant.
• Keep dates unambiguous when sharing results. A year-month-day date is easier to interpret internationally than a numeric date whose month and day order is unclear.

Frequently asked questions