Inputs
How to use
- Enter start and end date time values. If needed choose different timezones for each endpoint.
- Enable inclusive when your policy counts the exact end instant as part of the interval.
- Toggle business days to exclude weekends. Paste optional holidays as separate lines.
- Press Calculate. Review the calendar aware breakdown and the raw totals in days hours minutes seconds.
- Use Copy summary to paste results into tickets spreadsheets or chats.
Formula and method
We compute the interval as Δt = t₂ − t₁. For totals we convert both endpoints to UTC and subtract Unix timestamps to get exact seconds then derive minutes hours and days by integer division.
The human friendly breakdown uses the built‑in calendar aware DateTime::diff which accounts for leap years month lengths and daylight saving transitions. When inclusive is on we add one second to the end before computing differences.
Business day counting iterates dates in the chosen start timezone skipping Saturdays Sundays and any holiday lines that exactly match YYYY‑MM‑DD.
Why time zone awareness matters
Time zone differences can change the measured interval so this calculator lets you set separate zones for start and end values ensuring accurate comparisons across cities servers teams and schedules
Handling business days and holidays
Sometimes working days matter so you can exclude weekends and list custom holidays The tool counts days iterating dates and subtracting matches results for payroll planning scheduling reporting and compliance
Inclusive versus exclusive endpoints
Including the end instant adds one unit at the scale while exclusive treats the range as closed open Choose the option that matches billing attendance service level goals or analytics
Precision units and breakdowns
Breakdowns show years months days hours minutes seconds with totals per unit This clarifies deadlines dependencies and offsets You can compare options then export results to documentation trackers or messages
Validation tips and edge cases
Inputs validate ordering timezone names and formats Leap years month lengths and daylight saving transitions are handled Review results near boundary moments to confirm they match contract rules and needs
FAQs
Q1. What does inclusive endpoint mean?
When enabled the exact end instant is included by adding one second before computing the difference which aligns with inclusive count policies.
Q2. Which timezone should I pick?
Select the timezone that best represents the context of your event such as where the service level is defined or where the business operates.
Q3. How are business days calculated?
We count weekdays Monday through Friday and skip any custom holiday dates you provide. The count is based on the start timezone calendar.
Q4. Why do totals differ from component sums?
Totals are based on raw seconds while components are calendar aware. Month lengths leap years and daylight saving can make them differ.
Q5. Can I compare across different timezones?
Yes. Each endpoint can use a different timezone. The calculator normalizes to UTC for arithmetic while preserving calendar aware components.
Q6. How do I export results?
Use the Copy summary button then paste into your documentation issue tracker email or spreadsheet as needed.