Overnight Shift Calculator
Put both ends of your shift on the calendar. Compare clock readings with actual elapsed time when the clocks change.
Midnight is not the difficult part
The end date makes an overnight shift explicit. The time zone resolves the difficult part: missing or repeated hours when clocks change.
Calculations and file processing run in your browser. Saving on this device is optional. Privacy policy
On this page
Why overnight intervals need explicit start and end dates
An overnight shift calculator must know which calendar day each clock reading belongs to, because night work normally crosses midnight. A start of 22:00 and an end of 06:00 cannot be resolved from times alone, since 06:00 could mean earlier the same day or the following morning. Explicit start and end dates remove that ambiguity by anchoring each reading to a specific date. For example, March 7 to March 8 defines a forward interval across midnight, while identical times on the same date would be invalid or negative. This date-anchored approach also allows correct handling of calendar transitions, daylight saving changes, and clear records for later review. Without both dates, duration cannot be calculated reliably.
Reading 24-hour times across midnight
The 24-hour clock avoids morning and evening confusion by numbering hours from 00:00 to 23:59. Overnight math splits the interval at midnight and adds the two parts. From 22:00 to 24:00 is 2 hours, and from 00:00 to 06:00 is 6 hours, giving 8 clock hours for a next-date 22:00 to 06:00 shift. Other combinations work the same way: 23:00 to 07:00 is 8 hours, while 21:30 to 05:30 is also 8 hours. This method measures written clock readings, before any daylight saving adjustment. Understanding this baseline helps separate ordinary night shift hours from complications introduced by breaks, time zones, or clock changes. Enter evening start times correctly to preserve order.
Subtracting unpaid breaks recorded in minutes
Unpaid breaks are removed after the initial clock duration is found. The calculator uses break duration in minutes to keep partial hours precise and avoid decimal rounding errors. For example, 8 clock hours minus 30 unpaid minutes leaves 7 hours 30 minutes. A 60-minute break would leave 7 hours, while 45 minutes would leave 7 hours 15 minutes. Paid rests stay included; only unpaid durations are subtracted. Breaks that cross midnight do not need separate dates because they are treated as a duration, not a clock interval. Entering zero when no break was taken preserves a complete and auditable calculation trail. Minute-based entry makes comparisons across patterns more reliable.
Written clock readings compared with actual elapsed time
On ordinary dates, the difference shown by wall clocks equals physical elapsed time. On transition dates, those values can diverge. Written clock readings simply subtract the end reading from the start reading across midnight, always giving 8 hours for 22:00 to 06:00. Actual elapsed time measures seconds experienced in a specific time zone, which may be longer or shorter when clocks move. A supporting calculator therefore offers an optional actual elapsed mode alongside simple clock math. This distinction matters for accurate DST work hours, because payroll, rest, and fatigue analysis may depend on hours actually present rather than hours implied by dial positions. Both views prevent confusion when a night looks normal on paper but was altered by a clock shift.
Why the IANA time zone and real date matter
A time zone abbreviation is insufficient because the same local times can represent different physical periods in different places. The calculator therefore requires an IANA zone such as America/New_York or Australia/Lord_Howe, combined with explicit calendar dates. Real date and zone matter because daylight saving rules depend on both location and year, including rule changes over time. A March interval that springs forward in one zone may be ordinary elsewhere, and fall-back dates also vary by hemisphere. Selecting the correct zone ensures spring-forward gaps and fall-back repeats are applied only when they genuinely affect that shift. This matters for overnight work, where the transition often occurs mid-shift rather than in daylight.
Repeated hours and missing hours on transition nights
When clocks spring forward, the skipped interval creates nonexistent local times; for example, an end time inside the gap has no valid meaning. The calculator rejects nonexistent times rather than silently repairing them, requiring correction of the entered reading. When clocks fall back, the repeated hour creates two possible occurrences for the same reading, usually designated first and second. The calculator provides zone and occurrence choices so the intended instance can be selected. Verified illustrations include America/New_York March 7 2026 22:00 to March 8 06:00, which equals 7 elapsed hours with no breaks, and October 31 22:00 to November 1 06:00, which equals 9 elapsed hours because the repeated hour adds physical time.
Half-hour shifts, exportable records and limitations
Not every transition moves by one hour. Australia/Lord_Howe shifts by 30 minutes, so 2026-04-04 22:00 to 2026-04-05 06:00 equals 8.5 elapsed hours, demonstrating why fixed one-hour assumptions fail. A reliable workflow therefore records explicit dates, IANA zone, selected occurrence, clock duration, break minutes, and final result in an exportable trail for checking. These are example intervals, not global dates, and the same clock readings give different elapsed totals in other years or zones. Duration alone describes time present; it does not establish payable amounts or legal compliance, which depend on contracts, policies, and applicable regulations. Verification remains necessary for unusual or historical zones.
Questions, answered
Why must both start and end dates be entered for an overnight shift?
Because work spans midnight, the morning end time must be anchored to the next date to create a positive forward interval. Explicit dates also allow the correct transition rules to be applied for that specific night.
How are a 22:00 to 06:00 shift and a 30-minute break calculated?
Split the clock interval at midnight: 22:00 to 24:00 plus 00:00 to 06:00 equals 8 clock hours. Subtracting 30 unpaid minutes leaves 7 hours 30 minutes.
What is the difference between clock hours and elapsed hours?
Clock hours subtract the displayed readings. Elapsed hours measure physical time experienced in the selected IANA zone, which can differ when clocks move during the shift.
What happens if an entered time falls inside a spring-forward gap?
That local time never occurred. The calculator rejects nonexistent times rather than silently repairing them, so the reading must be corrected to a valid time.
How should the repeated hour during fall-back be handled?
Select the first or second occurrence for a reading inside the repeated hour. Each choice represents a different physical moment and produces a different elapsed total.
Why do identical 22:00 to 06:00 readings give 7, 9, or 8.5 hours in the examples?
Because real date and zone matter. America/New_York March 7 2026 to March 8 gives 7 elapsed hours, October 31 to November 1 gives 9 elapsed hours, and Australia/Lord_Howe 2026-04-04 to 2026-04-05 gives 8.5 hours through a 30-minute change. These are example intervals, not global dates.