WhenMathInternational Date-Line Event Planner
Enter one anchor moment in one zone and a list of zones to compare it against. This shows the exact local date and time in every zone for that same real instant, making visible when the calendar date itself, not just the clock, actually differs.
Worked example
One real instant, 1 AM on June 15 in Auckland, converts to 6 AM on June 14 in Los Angeles, a full calendar date earlier, because Auckland sits far enough ahead of Los Angeles that an early morning hour in Auckland still falls on the previous evening back across the Pacific. The same instant later in the Auckland day, say 11 PM, converts to a Los Angeles time that falls on the very same calendar date as Auckland, since by then enough of the day has passed in Auckland that subtracting the zone gap no longer crosses back over midnight in Los Angeles.
Common mistakes
- Assuming every pair of zones far apart in offset always shows a different date. Whether the date actually differs depends on the specific time of day, not just the offset gap.
- Reading the anchor zone's own date and time as if it were UTC. It is whatever local date and time you entered, resolved through the anchor zone specifically.
Limitations
This maps one single instant to multiple zones. It does not track a recurring event across many dates, which the DST Season Meeting Planner handles instead for a weekly recurring case.
Frequently asked questions
- How many zones can I compare at once?
- As many as you list, each resolved independently from the same underlying instant.
- Why do the results not just follow UTC offset order?
- They are sorted by each zone's own resulting local date and time, so a zone with a large positive or negative offset can still end up next to another zone whose local date happens to match.