Adding 2 hours 30 minutes to 9:00 AM gives 11:30 AM; the calculator carries minutes past 60 for you and flags any result that rolls into the next day.
Results computed in your browser.
Add 5 hours to 10:00 PM and you get 3:00 AM. But 3:00 AM of which day? That is the piece a plain calculator misses, and it is the whole reason this tool reports a day offset alongside the new time rather than just the time on its own.
Take 11:00 PM, which is 1,380 minutes since midnight, and add 3 hours, or 180 minutes. The total is 1,560 minutes, past the 1,440-minute mark that ends a day, so it wraps: subtract 1,440 and you get 120 minutes, which is 2:00 AM, one day later. Going the other direction, 1:00 AM minus 2 hours lands at 11:00 PM of the previous day. Both are the same arithmetic, just running in opposite directions across the midnight boundary.
| Start | Operation | Result | Day offset |
|---|---|---|---|
| 9:00 AM | add 2 h 30 m | 11:30 AM | Same day |
| 11:00 PM | add 3 h | 2:00 AM | +1 day |
| 1:00 AM | subtract 2 h | 11:00 PM | -1 day |
| 6:00 PM | subtract 9 h | 9:00 AM | Same day |
Every clock time here becomes minutes since midnight first. 9:00 AM is 540 minutes; adding 2 hours 30 minutes means adding 150, for 690 total. Divide 690 by 60 and the remainder gives you 11:30 AM. Subtracting works identically, just with a negative number going into the same conversion.
It has no idea what time zone you or anyone else is in. If you are trying to work out a local arrival time after a flight, use this tool to add the flight duration to your departure time first, then run that result through the time zone converter separately. Stacking both calculations in your head at once is where most travel-time math goes wrong.
The output here is always a clock time. Add 25 hours to any start and you land one calendar day later, one hour past the same clock reading, with a plus-one-day offset attached, correct but easy to misread if you were expecting a count of hours back instead. For that kind of total, the time or elapsed time calculator is the right tool.
Start at 10:15 PM and add 7 hours 50 minutes, the kind of sum that comes up when a delivery window or a rest period starts late in the evening. The tool converts 10:15 PM to 1,335 minutes since midnight, adds 470, and gets 1,805. That clears the 1,440-minute day boundary once, so it peels off one full day and keeps the remaining 365 minutes, which is 6:05 AM. The result panel shows exactly that: 6:05 AM (06:05), with a +1 day(s) offset attached. The 24-hour form in parentheses is there for anyone transferring the answer onto a schedule or time card that uses that notation.
One quiet use for subtract mode: figuring out whether there is enough turnaround between a late clock-out and the next morning's clock-in. Clock out at 11:30 PM with a 7:00 AM start tomorrow, and subtracting 11:30 PM from 7:00 AM across midnight leaves 7 hours 30 minutes of gap. Whether that gap is fine, tight, or a scheduling problem depends on your workplace and any scheduling rules that apply to it; what this tool contributes is the honest number, computed across the midnight boundary where mental arithmetic slips most. People chronically overestimate that gap by an hour when they work it out in their heads, always in the optimistic direction.
Because everything is converted to total minutes before any arithmetic happens, the tool cannot produce an answer like 9:75. Adding 50 minutes to 9:25 gives 615 minutes, which converts back as 10:15, the carry handled inside the division rather than as a separate step you could forget. That is the whole trick of the minutes-since-midnight method, and it is the same one worth borrowing if you ever do this math on paper: convert once, add or subtract plain numbers, convert back at the end.
This calculator runs on an idealized dial where every day holds exactly 1,440 minutes. Twice a year, American wall clocks disagree with that dial. On March 8, 2026, the stretch from 2:00 to 2:59 AM never happens: add 90 minutes to 1:00 AM and this page says 2:30, but a phone in Chicago that night reads 3:30. On November 1, 2026 the opposite trick runs and the 1 AM hour occurs twice. So treat the answer here as clock arithmetic, which is what it is. For anything spanning those two specific nights, or crossing a time zone, the elapsed hours differ from the dial answer by exactly one, and knowing which direction is the whole game.
Working backward from a fixed start time, the tidy method is to total the durations first and hit the clock once. Say a 9:00 AM appointment needs a 40-minute drive, 25 minutes of prep, and a 1-hour-5-minute errand before it. Those sum to 2 hours 10 minutes, and 9:00 AM minus 2:10 is 6:50 AM. Done on paper, that subtraction needs a borrow: 9:00 cannot give up 10 minutes, so it becomes 8:60, and 8:60 minus 2:10 falls out as 6:50. Same borrowing you learned for ordinary subtraction, except this column rolls over at 60 instead of 10, which is precisely the step people fumble and precisely what the minutes-since-midnight conversion makes impossible to fumble.
Interval schedules are this tool's quietest regular customer. Start something at 7:20 AM on a strict 6-hour cycle and the schedule marches around the clock without regard for your sleep:
| Round | Clock time | Day |
|---|---|---|
| 1st | 7:20 AM | Same day |
| 2nd | 1:20 PM | Same day |
| 3rd | 7:20 PM | Same day |
| 4th | 1:20 AM | +1 day |
The fourth round lands at 1:20 in the morning, and the fifth arrives back at 7:20 AM to restart the cycle. Any start time other than midnight puts one round in the middle of the night; that is arithmetic, not bad luck. A schedule written as "four times a day" usually means during waking hours and is a different instruction from "every 6 hours." When the wording matters, as it does with medication, follow the exact instruction you were given and ask the prescriber which one they meant.
The hours field takes fractions, which saves a conversion when a timesheet already speaks decimal. Type 7.75 hours with 0 minutes to add a 7-hour-45-minute workday: from a 6:30 AM start, that lands at 2:15 PM. Internally the tool multiplies the hours entry by 60 before doing anything else, so 7.75 becomes 465 minutes and joins whatever sits in the minutes field. If the translation itself is the thing you need, decimal to h:mm or back with nothing added, the decimal hours calculator does that one job on its own.
The 12-hour clock has exactly one genuinely confusing corner and it sits at the top of the dial: 12:00 AM is midnight and 12:00 PM is noon. Subtract 30 minutes from 12:15 PM and the correct answer is 11:45 AM, a jump from PM back to AM with no midnight anywhere near it. Add 30 minutes to 11:45 PM and you get 12:15 AM with a +1 day offset. Both results are easy to invert by half a day when transcribing. The parenthetical 24-hour form in the result panel, 00:15 versus 12:15, exists for exactly this hazard, and it is worth copying that form onto any schedule where an AM/PM flip would hurt.
Sources: NIST Time and Frequency FAQ.
Last updated July 18, 2026.
This tool only adds or subtracts a duration on a single clock; it does not know about time zones. For a flight, use this to add the flight duration, then use the time zone converter separately to shift that result into the destination zone.
Because a clock time alone can be ambiguous once you cross midnight. Adding 5 hours to 10:00 PM gives 3:00 AM, but 3:00 AM the next day, which is what the plus-one-day offset is telling you.
Yes. Choose Subtract, enter the end time as your start time, and enter how long the activity lasted. The result is when it began.
A time of day. If you have two clock times and want to know how much time passed between them instead, use the elapsed time calculator.
No practical one. Add 100 hours and the day offset will simply read a larger number, correctly showing how many calendar days the result rolled forward.
No, and on 363 nights a year that makes no difference. On the two US change nights, March 8 and November 1 in 2026, wall clocks skip or repeat an hour across 2:00 AM, so a result that crosses that moment sits one hour off what a local clock shows. Add or subtract the hour yourself for those nights.
Yes. The hours field accepts fractions and converts them to minutes internally, so 1.5 hours behaves exactly like entering 1 in hours and 30 in minutes. Both fields also combine, so 1.5 hours plus 15 minutes adds a total of 105 minutes.
Either run the tool repeatedly, feeding each result back in as the new start time, or total the durations first and add once. The answer comes out identical either way, since addition does not care about order; totaling first just means fewer chances to mistype.
12:00 AM is midnight and 12:00 PM is noon, the one spot where 12-hour notation trips nearly everyone. Check the 24-hour form shown in parentheses next to the result: 00:00 means midnight, 12:00 means noon, no ambiguity.