Calculation Methodology

Calendar dates and elapsed days

Date-only inputs use the Gregorian calendar and UTC-midnight anchors. Subtracting those anchors gives the calendar-day interval without local daylight-saving changes altering the count. The default elapsed interval excludes its end; an include-end control explicitly adds that named date.

Complete weeks use seven-day groups. Calendar months and years use completed anniversaries with month-end clamping. They are not approximated as 30-day months or 365-day years. The ordinary Gregorian date tools support four-digit years from 0001 through 9999.

Offsets and original anchors

Day and week offsets advance through real calendar dates. Month and year offsets keep the original day when it exists and clamp to the final valid date when it does not. A leap-day anniversary uses February 28 in a common year under this lab’s convention.

Recurring schedules calculate each occurrence directly from the original anchor. A January 31 monthly series can return to March 31 after a February clamp. A governing organization may specify another anniversary or adjustment convention.

Working dates and source coverage

Working-day tools first remove the selected weekends, then distinct custom closures and the selected public holiday records. A closure on an already excluded date is not deducted twice. An offset begins counting eligible dates after the starting date.

Nager.Date supplies requested country/year records. Countrywide and subdivision records are distinguished. Missing years prevent a source-aware result; earlier records are not silently repeated. Employer-specific rules and closures still need the visitor’s confirmed inputs.

Time zones and exact instants

Date-only today follows the selected IANA calendar zone. Local date-time tools interpret their inputs in the browser’s zone. UTC converters label their starting input explicitly. An exact-time countdown measures target instant minus current instant.

Available runtime time-zone rules determine local offsets, including clock changes. Ambiguous repeated local hours need a confirmed UTC instant or recorded offset. The browser Date model does not separately represent leap seconds.

Annual dates and changing years

Fixed dates, nth weekdays and Western Easter-related dates are calculated from reusable Gregorian rules. Next-occurrence pages choose the next date on or after today. Current headings, calendars and defaults advance with the actual request date; entered fixed dates remain fixed.

Meteorological season pages use Northern Hemisphere start dates. Deepavali and Chinese New Year pages state their country-specific holiday scope. Ramadan’s civil-calendar result is labeled as an estimate rather than a local moon-sighting announcement.

Published event schedules

The TV episode calendar requests dated broadcast records from TVmaze and displays its attribution. Future records appear when the provider publishes them. An empty future schedule is not a repeat of an earlier year.

One-time releases, sports fixtures and other editorial schedules need verified sources before they can be listed. Rule-generated dates and published schedule coverage are identified separately on their pages.

Primary references