Updated · Built and checked by the PlinzoTools team, formulas tested against published sources
Find the elapsed time between two full date-and-time timestamps.
2d 5h 30m 0s
This calculator finds the elapsed time between two full date-and-time timestamps, broken into days, hours, minutes, and seconds -- for spans that run longer than a single day, unlike the Time Duration Calculator, which assumes both times fall within one day.
Enter a start date/time and an end date/time. The result shows the elapsed span broken down by unit, plus a total-hours figure.
Total elapsed seconds = (end timestamp - start timestamp) in milliseconds, divided by 1000. That total is then broken into whole days, hours, minutes, and remaining seconds -- the standard stopwatch-style decomposition.
January 1, 2026 9:00 AM to January 3, 2026 2:30 PM is 2 days, 5 hours, 30 minutes.
For a same-day duration between two clock times, use the simpler Time Duration Calculator instead.
Fill in the full date and time for the start, then the full date and time for the end. Both must be in the same time zone, since the calculator reads each timestamp with your browser's local time. The result breaks the gap into days, hours, minutes, and seconds, and also shows the total in hours, which is handy when you need a single number for billing or logging.
A hypothetical job starts on March 3 at 6:20 PM and finishes on March 6 at 11:05 AM. From 6:20 PM on March 3 to 6:20 PM on March 5 is 2 days. From 6:20 PM to 11:05 AM the next morning is 16 hours 45 minutes. So the elapsed time is 2 days, 16 hours, 45 minutes. In total hours that is 2 times 24 plus 16.75, or 64.75 hours. Reading the total-hours figure is useful when a system needs a single decimal number rather than a days-and-hours breakdown.
Because the calculation uses your browser's local time, a span that crosses a daylight saving change can come out an hour longer or shorter than the wall-clock difference suggests. For example, on the night clocks move forward, the local day is only 23 hours long, so the elapsed time between two clock readings can be one hour less than a simple subtraction would suggest. If precision across such a boundary matters, enter both timestamps in a zone that does not observe daylight saving, or double-check the result against your source records.
It works well for measuring how long a multi-day task, shipment, outage, or contract review actually took, for computing how long ago an event happened, or for documenting elapsed time in a report. For a specific number of calendar months or business days rather than raw elapsed time, use a date calculator instead.
The result is clamped to zero rather than showing a negative duration -- double-check your inputs if you expect a positive elapsed time.
Both timestamps are read using your browser's local time zone, so keep both entries in the same time zone for an accurate result.
Yes -- there's no upper limit; the day count simply grows to reflect any span length.
The end timestamp is at or before the start, so the result is clamped to zero. Check that the start and end are not swapped.
Read the total-hours figure in the result, which converts the whole span, including days, into hours.
It can. Local time is used, so a span across a clock change may differ by an hour from a simple subtraction of the two clock readings.
Reference: U.S. Department of Labor