Calculate elapsed clock time from strict 24-hour readings with an explicit same-day or next-day choice and auditable seconds.
A quick decision brief for this specific tool
Two strict 24-hour clock readings plus an explicit same-calendar-day or next-calendar-day selection
Elapsed hours/minutes/seconds, decimal hours, total minutes, total seconds and the retained end-day choice
Parses exact HH:MM or HH:MM:SS values, adds 24 hours only when Next calendar day is selected, then subtracts the start; malformed clocks and implicit overnight wrapping are rejected
Choose your path
Calculate elapsed clock time from two strict 24-hour readings and an explicit same-day/next-day choice without silently inferring overnight wrap, breaks, dates, zones or DST.
Reconcile exact start/end readings without an invented break.
Enter both clock readings, keep Same calendar day, then compare total hours/minutes/seconds.
Gets reproducible elapsed arithmetic and deducts documented breaks separately.
Avoid a negative or silently wrapped duration.
Enter the late start, early end, and explicitly choose Next calendar day.
Sees the retained next-day choice and exact subtraction.
Recognize when clock-only arithmetic is insufficient.
Review the scope check and move to full dated named-zone records.
Does not use two bare clock readings for a DST or time-zone interval.
Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.
This tool is part of these guided projects. Each project provides step-by-step instructions with checklists and all the tools you need in one place.
Tools you might need next
Compare explicit from and target dates as future, same-date, or past with signed calendar days, weeks plus days, and a clear zero-day convention.
Convert a clock between explicit fixed UTC offsets, including quarter-hour offsets, with UTC intermediate and calendar-day shift.
Calculate a strict calendar difference, elapsed days, inclusive dates, completed months, and Mon–Fri dates without DST off-by-one errors.
Each reading must match HH:MM or HH:MM:SS on a 24-hour clock. Invalid hours, minutes, seconds, extra tokens, and partial formats are rejected.
clock seconds = hour × 3600 + minute × 60 + secondSame-day subtraction uses the two readings directly. Next-day subtraction adds exactly 86,400 clock seconds to the end before subtracting; the tool never guesses overnight intent.
elapsed = end + stated day offset − startThe result decomposes the same elapsed-seconds value into hours, minutes and seconds and also shows decimal hours and total minutes. Breaks, payroll rounding, dates, zones and DST remain external.
Updated: August 2026
A technician records 09:10:15 to 14:45:50 on the same day and keeps the exact seconds for a reproducible log.
An operator enters 22:45:30 to 06:15:00 and explicitly chooses Next calendar day, then subtracts any documented break outside the tool.
A coordinator recognizes that two clock readings around a DST transition are insufficient and switches to dated named-zone timestamps.
Select Next calendar day explicitly; same-day earlier-end input is rejected.
Apply the governing break/rounding policy and use full dated named-zone timestamps when civil-time rules matter.
Enter two strict 24-hour clock readings and state whether the end is on the same or next calendar day. The result preserves that choice and does not invent breaks, dates, time zones, or daylight-saving rules.