How to Calculate Elapsed Time Between Two Events
Reviewed by Jerry Croteau, Founder & Editor
Table of Contents
I was staring at two timestamps and my brain just… stalled
I was standing in the lumber aisle doing math on my phone and nothing was adding up. I had a delivery window that started at 9:12 and ended at 11:47 and the guy at the counter was like “so it’s basically 2.5 hours, right?” and I nodded like I understood. I didn’t. Because 9:12 to 11:47 isn’t “half” anything, and the more you try to eyeball it, the more you end up paying for the wrong thing (or showing up late, which is honestly worse).
So yeah, elapsed time sounds simple until you’re doing it fast, in the real world, with someone waiting on you.
Here’s how I do it now, and how you can do it without getting cute.
Elapsed time is just “end minus start”… but you’ve gotta subtract it like a grown-up
Elapsed time means the duration between two events. That’s it. Not “what time is it,” not “how many hours are left,” just: start time → end time → difference.
And the thing is, time subtraction is annoying because it’s base-60. Minutes roll over at 60, not 10, so you can’t treat 11:05 − 9:50 like normal subtraction unless you borrow an hour. If you’ve ever done 5 − 50 and felt your soul leave your body, same vibe.
So here are the three ways that actually work, depending on what you’re doing:
- “Borrowing” method (fast in your head): good for same-day times like 9:12 to 11:47.
- Convert to minutes (hard to mess up): good when you’re tired or it crosses hours weirdly.
- Use a calculator (no shame): good when it crosses midnight, spans days, or includes seconds.
And if you just want the tool right now, I built these for exactly this kind of “I need the answer, not a lecture” moment:
Also handy when you’re bouncing between units:
Don’t overthink it.
The method I actually use: convert both times to minutes (then convert back)
This is the one I lean on when I’m doing real work and I don’t want to “trust my vibe.” Convert the start time to total minutes since midnight, do the same for the end time, subtract, then turn the result back into hours and minutes. It sounds like extra steps, but it’s weirdly calming because every step is dumb-simple.
Let’s run that lumber-aisle example: start at 9:12, end at 11:47.
- Convert start time to minutes:
9 × 60 = 540 minutes
540 + 12 = 552 minutes - Convert end time to minutes:
11 × 60 = 660 minutes
660 + 47 = 707 minutes - Subtract:
707 − 552 = 155 minutes - Convert 155 minutes back:
155 ÷ 60 = 2 hours remainder 35 minutes → 2 hours 35 minutes
That’s the real answer. Not “about 2.5.” It’s 2 hours and 35 minutes. And if you’re billing labor, scheduling a pickup, logging equipment runtime, tracking a workout, whatever… that extra 5 minutes here and 10 minutes there adds up.
And if you want to skip the manual steps (because you’re literally holding a ladder), drop the times into this:
It’s not fancy. It’s just correct.
Crossing midnight is where people blow it
But what if the start time is 22:40 and the end time is 01:15? That’s the one that makes people throw out a number and hope nobody checks. And I get it — your brain wants to say “end is smaller than start, so… negative?”
Here’s the trick: treat midnight like a boundary. You’re really doing two chunks of time: start → 24:00, then 00:00 → end.
Example: 22:40 to 01:15.
- 22:40 to 24:00 is 1 hour 20 minutes
- 00:00 to 01:15 is 1 hour 15 minutes
- Total elapsed = 2 hours 35 minutes
Same answer as earlier, which is kind of funny, but yeah. And if you’re doing the “convert to minutes” method, you just add 24 hours (1440 minutes) to the end time when it’s on the next day.
So in minutes:
- Start: 22:40 → 22×60 + 40 = 1360
- End: 01:15 → 1×60 + 15 = 75, but next day so 75 + 1440 = 1515
- Elapsed: 1515 − 1360 = 155 minutes → 2 hours 35 minutes
That “add 1440” move is the whole game for overnight shifts, travel, baking timers that run past midnight, you name it.
Quick reference table (because you’ll see these constantly)
I keep little mental anchors for conversions so I don’t waste time. Here are a few that come up all the time when you’re turning elapsed minutes into something you can say out loud.
| Elapsed minutes | Hours + minutes | Where it shows up |
|---|---|---|
| 15 | 0 hr 15 min | Quick pickup window |
| 30 | 0 hr 30 min | Half-hour billing blocks (common) |
| 90 | 1 hr 30 min | Drive time + unload |
| 155 | 2 hr 35 min | My “why doesn’t this feel like 2.5?” example |
| 240 | 4 hr 0 min | Morning shift chunk |
If you’re converting back and forth a lot, these two links save brainpower:
And yes, people argue about rounding.
FAQ (the stuff people text me about)
How do I calculate elapsed time in hours as a decimal?
Take the elapsed minutes and divide by 60. Example: 155 minutes ÷ 60 = 2.5833… hours (so you’d write 2.58 hours if you’re rounding to two decimals). If you already have hours and minutes, do: hours + (minutes ÷ 60).
Why is “2 hours 35 minutes” not the same as “2.35 hours”?
Because .35 of an hour is not 35 minutes. It’s 0.35 × 60 = 21 minutes. The decimal part is a fraction of 60 minutes, not a “minutes-looking” number. This is the one that quietly wrecks invoices.
What if my times include seconds?
- Convert everything to total seconds (hours × 3600 + minutes × 60 + seconds).
- Subtract end − start.
- Convert back: divide by 3600 for hours, then remainder ÷ 60 for minutes, remainder is seconds.
If you’re dealing with 24-hour clocks and you keep second-guessing yourself, use the
And if you just want a clean “start/end → duration” answer without the ceremony, use
That’s it — subtract time like it’s base-60, not base-10, and you’ll stop getting surprised by “missing” minutes. And honestly, once you do the minutes-since-midnight trick a few times, you’ll wonder why you ever tried to eyeball it!
Related Calculators
Get smarter with numbers
Weekly calculator breakdowns, data stories, and financial insights. No spam.
Discussion
Be the first to comment!
