How to calculate time durations correctly
Why time maths goes wrong, and a reliable method that does not.
Working out the time between two moments sounds trivial until you actually try it — crossing midnight, spanning several days, juggling hours and minutes that do not divide neatly, or adding up a week of logged time. Time arithmetic is genuinely error-prone because it is not decimal: sixty seconds to a minute, sixty minutes to an hour, twenty-four hours to a day. This guide explains how to calculate durations reliably and where the common mistakes hide.
Calculating how much time has passed or how long something will take is one of those everyday tasks that feels like it should be effortless but quietly causes errors — in timesheets, in travel plans, in project schedules, in billing. The reason is that time does not obey the base-ten arithmetic our brains default to, so subtracting two clock times or adding up a list of durations invites small mistakes that compound. Learning a reliable method, and knowing where the traps are, turns a fiddly chore into something you can do quickly and trust.
Why time maths is tricky
Everyday arithmetic is base-10, but time is not. Sixty seconds make a minute, sixty minutes make an hour, and twenty-four hours make a day — so you cannot simply subtract times as if they were decimals. The difference between 2:45 and 4:30 is not "1.85 hours" read off the digits; it is 1 hour and 45 minutes. Mixing decimal thinking into time calculations is the root of most errors. A time duration converter handles the base-60 arithmetic for you, but understanding the traps helps you sanity-check results.
The reliable method: convert to one unit
The dependable way to find a duration is to convert both times into a single small unit — usually minutes — do the subtraction, then convert back. To find the gap between 9:15 and 14:40: 9:15 is (9 × 60) + 15 = 555 minutes past midnight; 14:40 is (14 × 60) + 40 = 880 minutes. The difference is 880 − 555 = 325 minutes, which is 5 hours and 25 minutes. Converting to a single unit first removes the borrowing errors that plague direct subtraction of hours and minutes.
Crossing midnight
The classic trap is a period that spans midnight — a night shift, a flight, a sleep log. If the end time is earlier on the clock than the start time, the period crossed midnight, and you must add 24 hours (or 1,440 minutes) to the end before subtracting. From 22:30 to 06:15: treat 06:15 as 30:15 (adding 24 hours), giving (30 × 60 + 15) − (22 × 60 + 30) = 1,815 − 1,350 = 465 minutes, which is 7 hours 45 minutes. Forgetting to add the day is why manual shift calculations so often come out negative or wildly wrong.
Adding and subtracting durations
To add durations — say three tasks of 1:45, 2:30, and 0:50 — add the minutes and hours separately, then carry. Minutes: 45 + 30 + 50 = 125 minutes = 2 hours 5 minutes. Hours: 1 + 2 + 0 = 3, plus the 2 carried = 5. Total 5:05. The carry step, converting every 60 minutes into an hour, is where mistakes creep in if you rush. Keeping minutes and hours in separate columns and carrying deliberately keeps it correct.
Decimal hours for pay and billing
Timesheets and invoices often need durations as decimal hours rather than hours and minutes, because you multiply them by a rate. The conversion is to divide the minutes by 60: 45 minutes is 45 ÷ 60 = 0.75 hours, so 2 hours 45 minutes is 2.75 hours. The frequent error is writing 2 hours 45 minutes as "2.45 hours", which is wrong — the minutes are not a decimal fraction until you divide by 60. Getting this right matters directly to what you are paid or what you bill.
Working across days
For durations spanning several days — a project timeline, a trip, an elapsed-time log — the safest approach is to work in total hours or even total minutes from a common starting point, rather than juggling days, hours, and minutes together. Three days and five hours is (3 × 24) + 5 = 77 hours. Converting everything to one unit, doing the arithmetic, then translating back to days-and-hours at the end avoids compounding small errors across each boundary.
Time zones add another layer
When start and end are in different time zones — a call between cities, an international flight — you must account for the offset before calculating duration. A flight that leaves at 10:00 in one zone and lands at 14:00 in a zone three hours ahead did not take four hours; converting both to a single reference (such as UTC) before subtracting gives the true elapsed time. Ignoring the offset is a common source of "impossible" flight durations. Reducing both times to one zone first makes the calculation ordinary again.
Practical uses
Duration calculations turn up everywhere: totalling worked hours for a timesheet, planning how long a journey with connections will take, measuring how long a task actually took versus the estimate, counting down to a deadline, or working out age or tenure in precise terms. In each case the same principles apply — convert to a single unit, watch for midnight and day boundaries, handle time zones first, and keep decimal-hour conversions honest. A converter that manages the base-60 arithmetic frees you to focus on the plan rather than the sums.
Quick answers to common questions
How do I calculate hours between two times? Convert both to minutes past midnight, subtract, then convert back to hours and minutes.
How do I handle a shift that crosses midnight? Add 24 hours to the end time before subtracting the start.
How do I convert minutes to decimal hours? Divide by 60 — 45 minutes is 0.75 hours, not 0.45.
Why is time hard to add? It is base-60, not decimal, so every 60 minutes carries into an hour.
The bottom line
Time is base-60, not decimal, which is why durations are easy to get wrong. Convert both times to a single unit before subtracting, add 24 hours when a period crosses midnight, handle time zones by reducing to one reference first, and divide minutes by 60 for honest decimal hours. Follow those rules and time arithmetic becomes reliable — and a duration converter takes care of the fiddly parts.
Related tools
- Time Duration Converter — Convert milliseconds through centuries, using Gregorian averages for months and years.
- Common Unit Systems Converter — Compare metric, imperial and US customary measures side by side and learn how they differ.
- Media Bitrate & File Size Calculator — Estimate video and audio file sizes, required bitrates and storage from duration and quality.
- Shoe & Clothing Size Converter — Convert shoe and clothing sizes between US, UK, EU and Japanese standards for men, women and children.