How to Calculate Elapsed Time

A livestream “started 2 hours ago.” A workout “has been going for 40 minutes.” A support ticket has “been open 3 days.” Every one of these is elapsed time — a measurement that keeps counting up from a fixed starting point, rather than a gap between two times that were both already settled. Because the end point is “now,” and now never sits still, elapsed time behaves a little differently from an ordinary clock-time subtraction.

This page covers the general elapsed-time formula, the specific case of measuring from a past moment up to the present, and the extra step a stopwatch adds when it gets paused along the way. If both your start and end times are already fixed and known — a meeting that ran from 09:00 to 09:45, say — the guide to calculating duration between two times covers that case directly.

Elapsed time is the amount of time that has passed between a starting point and an ending point — nothing more exotic than that. What sets it apart from a plain “time between two times” question is the starting point's relationship to now: elapsed time is very often still running, measured from a fixed start up to the present moment rather than between two points that were both already fixed in the past.

When both the start and the end are already known and fixed, that's a duration, and the site's guide to duration between two times covers the full method for that case. Elapsed time is the broader idea that also covers the open-ended case — measuring from then until right now — which is what the rest of this page focuses on.

Every version of elapsed time uses the same shape: elapsed = end point − start point. What changes is what you plug in for the end point, and which unit you report the answer in.

If both points are known clock times on the same day, the end point is simply that later time — the general rules for adding and subtracting those values are covered in how to add and subtract time. If you're measuring up to right now, the end point is the current time, and it keeps moving — which is why an elapsed-time reading is only accurate at the instant you check it. If a stopwatch was paused along the way, the paused stretches don't count and get subtracted out before the formula runs (covered in §5).

This is the version people usually mean when they ask “how long has it been since…” You need two things: the start time and the current time. If the start happened earlier today, subtract directly; if it happened last night, the same midnight-crossing adjustment described in how many hours between two times applies — add 24 hours' worth of minutes before subtracting.

For a running count that doesn't require redoing this by hand every few minutes, the time-ago calculator keeps counting on its own.

Enter a time from earlier today (or last night) and watch the elapsed time count up in real time.

A stopwatch — literal or a phone timer — adds one wrinkle the formula above doesn't have: pauses. If you start a timer at the beginning of a task, pause it for interruptions, and stop it at the end, the elapsed time you actually want is the running time, not the wall-clock time from first start to final stop.

Report elapsed time in whatever unit the audience will actually picture. A 90-second sprint interval is clearer as “90 seconds” than “0.025 hours”; an 11-hour flight is clearer in hours than in 660 minutes. As a rough guide: seconds and minutes for anything under about an hour, hours (and hours-plus-minutes) from an hour up to a couple of days, and days beyond that.

If you do need to convert between units — minutes to hours, or hours into a decimal figure for a timesheet — the site's unit converters and the minutes-to-decimal-hours guide handle the arithmetic. There's no separate rule for elapsed time specifically once you have the raw minutes or seconds in hand.

• Fitness — workout duration, rest intervals, and race splits, often on a literal stopwatch.
• Live events — “started 2 hours ago” labels on livestreams and broadcasts.
• Cooking — how long something has already been in the oven.
• Project and task tracking — how long a ticket has been open.
• Customer-facing “time since” labels — “posted 3 hours ago,” “last seen 2 days ago.”

• Forgetting to subtract paused time in a stopwatch measurement — the wall-clock trap from §5.
• Not adjusting for a start time that actually happened yesterday, producing a negative or nonsensical result.
• Converting to a different unit too early and rounding twice, which compounds small errors.
• Treating “elapsed” and “remaining” as the same thing — elapsed counts up from the start, remaining counts down to a future end point, and mixing the two up flips the whole answer.