Enter a start and end date-time in your browser's local calendar to measure elapsed time. The calculator returns calendar components plus total hours, minutes, and seconds. An end before the start is rejected instead of shown as a negative duration.
Read days, hours, minutes, and seconds as the decomposition; read totals as aggregate values. At month and year boundaries, calendar units preserve date shape while totals describe elapsed seconds. This suits appointments, trips, reservations, and shifts. It is not legal-age, contractual-deadline, payroll, or holiday-entitlement advice; age planning should follow the engine's February 29-to-February 28 convention, not a jurisdiction-specific rule.
How this is calculated
The runtime parses valid datetime-local values in the browser's local convention and uses calendar-aware components alongside elapsed seconds. Total minutes and hours are floored from elapsed seconds. This is elapsed duration, not working time, billable time, holiday time, or timezone conversion.
Assumptions and limits
Inputs use YYYY-MM-DDTHH:mm and represent the same local-time convention; the page has no IANA timezone selector.
The end must be at or after the start. Same-moment endpoints are valid and produce zero totals.
Calendar components and aggregate totals answer different questions; a month or year is not a fixed number of hours.
Breaks, holidays, business hours, payroll rules, and legal deadlines require a separate policy and calculator.
Result: 1 calendar year; 8,760 total hours; 525,600 total minutes; 31,536,000 total seconds
The year component preserves calendar meaning while totals provide an aggregate reporting value.
Boundary cases
Reversed endpoints produce no result and the UI asks for an end after the start. The tool does not return a signed duration.
Month and year boundaries can change calendar components while totals remain based on elapsed seconds.
A browser-local duration cannot resolve records from different locations. Reject a DST gap; for a repeated fall-back hour, confirm the UTC offset.
Business-day ranges include both endpoints, advancement excludes the start, and the UI displays an unsigned reversed-range count. Deadline counting reduces a positive amount by one even on a weekend; it is weekend-only with no regional holiday selector.
A weekend or holiday does not pause elapsed duration. Do not interpret this result as a workday count.
Common mistakes
Entering only clock times for an overnight interval instead of entering the next date.
Calling elapsed duration paid work, billable time, or business hours.
Assuming every month or year has one fixed duration.
Comparing locations without agreeing on a timezone and offset.
Expecting a reversed pair to return a negative value.
Does the calculator include the start date or minute?
It measures from the starting date-time to the ending date-time; the start is the interval's beginning, not an inclusive date count.
Can the duration cross midnight, a month, or a year?
Yes. Enter the date and time at both endpoints; the engine handles boundaries and exposes totals.
Why is a full year not best read as a fixed day count?
Calendar years and months vary. The runtime preserves components and calculates totals from elapsed seconds.
Does this account for time zones or daylight saving time?
The page compares browser-local values and has no IANA selector. Normalize locations with the Time Zone Converter and verify DST gaps or repeated fall-back times.
What should I use for a workday deadline?
Use a business-day or deadline tool and record its convention. Duration does not remove weekends, holidays, breaks, or business-hour limits.