Quick guide
How to use this calculator
- Choose the exact calendar, clock, recurrence, time-zone, working-day, or endpoint convention before entering values.
- Add one structured row for each participant, interval, stage, closure, target, or period that belongs in the scenario.
- Check the component ledger before using the headline result: it exposes skipped dates, offsets, transitions, overlaps, stage boundaries, and the convention driving the answer.
Calculation method
Explicit date and time workflow
Resolve the source local wall time to a unique UTC instant under the selected ambiguity rule, then format that instant in each target zone.
The calculator keeps civil dates, elapsed durations, local clock readings, UTC instants, work calendars, and recurring rules distinct rather than silently treating them as interchangeable.
Worked example
Worked example
A Paris meeting converted to New York can differ by five or six hours depending on the date's DST rules.
Resolve the source local wall time to a unique UTC instant under the selected ambiguity rule, then format that instant in each target zone.
Supported inputs
Precision and limits
Calendar and time-zone conventions
Gregorian dates and IANA named zones are modeled explicitly. Holiday, school, legal, payroll, contractual, and operating calendars are never inferred from a country name.
DST and civil-time limits
Repeated or nonexistent local clock readings are identified where they matter. Future government time-zone changes cannot be predicted beyond the time-zone data available to the runtime.
Planning support, not authority
Results organize entered assumptions. They do not determine legal notice, payroll compliance, staffing safety, entitlement, service credits, travel feasibility, or institutional policy.
Calculator-specific boundary
Time-zone laws change. The page must disclose its bundled/runtime tzdb environment and reject nonexistent local times; repeated times require earlier/later selection.
Continue calculating
