The add and subtract time calculator above performs clock arithmetic: you give it a starting time and an amount of time to add or take away, and it returns the resulting clock time along with how many days the result has moved forward or back. Add 3 hours 45 minutes to 14:20 and you get 18:05 on the same day. Add 2 hours 30 minutes to 23:40 and you get 02:10 the following day — the rollover being the part that trips up manual calculation.
This tool answers a different question from a duration calculator. Here you know a starting time and a length, and you want the end time. If you already know two times and want the gap between them, use our time duration calculator instead. Arb Digital keeps them as separate pages because merging both directions into one interface makes both harder to use.
What This Add and Subtract Time Calculator Does
It takes a clock time down to the second, applies a positive or negative offset expressed in hours, minutes and seconds, and reports the result in both 24-hour and 12-hour notation. Alongside that it shows the day rollover — whether the answer lands on the same day, the next day, two days later, or a previous day — plus the total size of the offset in minutes and in decimal hours, which is useful when you need to feed the same figure into a system that expects a decimal.
Offset values are not restricted to sensible ranges. Entering 90 minutes is treated as an hour and a half. Entering 200 hours is treated as eight days and eight hours, and the rollover figure reports it correctly. That matters because real inputs often come from a system that reports everything in minutes, and having to convert before you can use a calculator defeats the point.
How to Use It
- Enter the start time. Seconds are optional — leave them at zero if you are working to the minute.
- Choose add or subtract. Subtracting past midnight is handled the same way as adding past it, just in the other direction.
- Enter the offset in hours, minutes and seconds. Any of the three can be left at zero, and values above 59 are absorbed correctly.
- Read the resulting time and the rollover. The rollover line tells you whether the answer is on the same day or a different one, which is the piece a raw clock time cannot express.
- Press Calculate to update, or Reset to return to the worked example of 14:20 plus 3 hours 45 minutes.
The Formula: Modular Arithmetic on the Clock
Clock time is modular arithmetic with a modulus of 86,400 seconds — the number of seconds in a day. The method is to convert the start time to seconds past midnight, convert the offset to seconds, add or subtract, then take the result modulo 86,400 to get the clock time and the whole-day quotient to get the rollover.
Take the default example. 14:20 is 14 × 3,600 + 20 × 60 = 51,600 seconds. The offset of 3 hours 45 minutes is 13,500 seconds. Adding gives 65,100 seconds, which is under 86,400, so the day does not change. Converting back: 18 × 3,600 = 64,800, leaving a remainder of 300 seconds, and 300 ÷ 60 = 5 minutes. The result is 18:05. Doing the same sum in hours and minutes columns means carrying 65 minutes into the hour column, which is where hand calculation usually goes wrong.
Now the rollover case. 23:40 is 85,200 seconds. Adding 2 hours 30 minutes (9,000 seconds) gives 94,200. That exceeds 86,400, so subtract one day: 94,200 − 86,400 = 7,800 seconds, which is 2 hours 10 minutes. The result is 02:10, plus one day. Going the other way, subtracting 3 hours from 01:15 gives a negative number, so add 86,400 back and record a rollover of minus one day.
Why Negative Time Is the Hard Case
Most languages implement the modulo operator so that a negative dividend produces a negative remainder. In JavaScript, −3,600 % 86,400 is −3,600, not 82,800. Code that assumes modulo always returns a non-negative value will produce impossible clock times such as −1:00 whenever a subtraction crosses midnight backwards. The fix is to add the modulus and take the remainder again, which is what this calculator does internally.
This is not a theoretical concern. It is one of the most common bugs in hand-rolled time handling, and it only appears for inputs that cross midnight backwards, so it survives casual testing and shows up months later on a night shift. If you are working with epoch timestamps rather than clock times, the Unix timestamp converter avoids the problem entirely by working in absolute seconds with no wraparound.
Rollover Is Information, Not a Rounding Error
A clock time carries no date. "02:10" is a complete answer to "what time will it be" and a useless answer to "when should I be there", because the two differ by a day. Any system that stores only the clock time and discards the rollover has thrown away half the answer, and the failure mode is always the same: something is scheduled 24 hours away from where it was meant to be.
This is why the rollover figure is given its own place in the results rather than being folded into a note. If you are adding a long offset — a 72-hour turnaround, a five-day processing window — the day count is the more important half of the output. For offsets measured in days rather than hours, calculate the date side with the date difference calculator or the days until date calculator, and use this tool for the hours and minutes within the day.
Where Clock Arithmetic Stops Being Reliable
Two things break the assumption that a day is exactly 86,400 seconds. The first is daylight saving time. In regions that observe it, one day each year has 23 hours and another has 25. Adding 12 hours to a time on a transition date gives a clock result that is an hour off from the elapsed-time result, and neither is wrong — they are answering different questions. Wall-clock arithmetic and elapsed-time arithmetic genuinely diverge on those two days.
The second is leap seconds, which are inserted occasionally to keep atomic time aligned with the Earth's rotation. These are announced only months in advance by the International Earth Rotation and Reference Systems Service and produce a minute containing 61 seconds. For everyday scheduling they are irrelevant; for anything that measures intervals to sub-second precision they are not. The way civil time is defined and distributed is documented by the NIST Time and Frequency Division.
This calculator performs pure wall-clock arithmetic on a 24-hour day and does not adjust for either. If your calculation spans a daylight saving transition, work out the clock answer here and then apply the hour manually. If it spans time zones as well, resolve the zones first with the time zone converter and do the arithmetic in a single zone.
Practical Uses Beyond Scheduling
Cooking and process timing is the everyday case: a dish that needs four hours twenty minutes and has to be ready at 19:30 needs to go in at 15:10, which is subtraction rather than addition. Broadcast and event running orders are another: a two-hour fifteen-minute programme starting at 21:50 finishes at 00:05 the next day, and the rollover is what tells the schedule to list it under tomorrow.
Service-level agreements are the business case. A four-hour response window on a ticket raised at 16:45 expires at 20:45, but a next-business-day window raised at the same time expires on a completely different basis and needs the business days calculator instead. Knowing which kind of window you are working with matters more than the arithmetic itself.
Arb Digital builds booking systems, appointment tools and client portals where rollover, time zones and daylight saving are handled explicitly rather than discovered in production.
Web Development Services Talk to Arb DigitalCommon Mistakes to Avoid
- Dropping the day rollover — 02:10 the next day and 02:10 today look identical once the rollover is discarded, and the gap is a full 24 hours.
- Assuming modulo returns a positive number — subtracting backwards past midnight produces negative remainders in most languages, and impossible clock times as a result.
- Adding hours and minutes in separate columns — carrying from minutes to hours by hand fails as soon as the minutes exceed 59, which is most of the time.
- Treating 12:00 AM and 12:00 PM as interchangeable — midnight is 00:00 and noon is 12:00, and the twelve-hour clock names them in a way that invites exactly this error.
- Doing wall-clock arithmetic across a daylight saving change — the elapsed time and the clock difference genuinely disagree by an hour on those two days a year.
Related Free Tools From Arb Digital
Use the time duration calculator when you have two times and want the gap, the time converter for straight unit conversion between seconds, minutes, hours and days, the time card calculator for a week of shifts, and the time zone converter when the two times sit in different regions. The full free online tools hub has the rest of the set.
Frequently Asked Questions
18:05 on the same day. Converting to seconds past midnight gives 51,600 plus 13,500 equals 65,100 seconds, which is 18 hours and 300 seconds, or 18:05. The total stays under 86,400 seconds, so there is no day rollover.
Add the offset in seconds, then subtract 86,400 for each whole day the total exceeds. 23:40 plus 2 hours 30 minutes gives 94,200 seconds; subtracting one day leaves 7,800 seconds, which is 02:10 on the following day.
The result rolls back into the previous day. Subtracting 3 hours from 01:15 gives 22:15 on the day before, and the rollover figure shows minus one day so the date side is not lost.
Yes. Values above 59 are absorbed correctly, so 90 minutes is treated as 1 hour 30 minutes and 200 hours is treated as 8 days and 8 hours. The rollover figure reports the whole days separately.
This tool takes a start time and a length and returns an end time. A duration calculator takes two times and returns the length between them. They are opposite operations, and using the wrong one is the most common reason an answer looks nonsensical.
No. It performs wall-clock arithmetic on a fixed 24-hour day. On the two transition days each year the elapsed time and the clock difference genuinely disagree by an hour, so that hour has to be applied by hand.
Because many payroll, billing and project systems accept only decimal hours. Showing the offset as both a minute count and a decimal saves converting it separately and removes the risk of writing 3h 45m as 3.45 instead of 3.75.
