ReckonDay

Methodology

Every calculator on ReckonDay runs on one shared, unit-tested date-math engine rather than a separate hand-rolled implementation per tool. This page documents the actual rules that engine follows, so the reasoning behind any specific result is checkable rather than a black box.

Leap years. ReckonDay follows the standard Gregorian rule: a year divisible by 4 is a leap year, except century years (divisible by 100), which are not leap years, except years divisible by 400, which are leap years after all. 1900 was not a leap year; 2000 was; 2100 will not be. This three-tier rule keeps the calendar's long-run average year length at 365.2425 days, correcting the Julian calendar's simpler (and slightly overcounting) 365.25-day average.

Month-end date addition. When adding or subtracting whole calendar months or years lands on a day that doesn't exist in the target month (for example, January 31st plus one month), the result is clamped to that month's last valid day (February 28th or 29th) rather than rolled forward into the next month. This convention is stated explicitly on the Date Plus or Minus Days tool and applied consistently everywhere else on the site that performs month/year-based date arithmetic.

Weekday calculation. Weekdays are computed with a direct modular-arithmetic routine (in the spirit of Zeller's congruence) rather than a bounded lookup table, so it works identically for a date next week or a thousand years away. For dates before the Gregorian calendar's real historical adoption (1582 in much of Europe; 1752 in Britain and its colonies), the engine uses the standard "proleptic" convention of projecting today's calendar rules backward — standard practice for date-math software, but not necessarily what a calendar actually in use at the time would have shown.

ISO-8601 vs. US week numbers. By default, week numbers follow ISO-8601: week 1 of a year is the week containing that year's first Thursday, and weeks run Monday to Sunday. This means the very last days of December can belong to week 1 of the following year, and the first few days of January can belong to week 52 or 53 of the previous year. An alternative US-style, Sunday-start, January-1-anchored convention is also available on the Week Number Calculator, since spreadsheet software (notably Excel's default WEEKNUM behavior) commonly uses that convention instead.

Business days and weekends. The default weekend definition is Saturday-Sunday, adjustable to Friday-Saturday for countries (including several in the Middle East) that use that convention instead. Business-day calculations optionally exclude a selected country's fixed-date public holidays, sourced from that country's official government holiday calendar as of 2026-07-12. Movable and lunar-calendar holidays (Easter-linked observances, Lunar New Year, Diwali, Ramadan, and similar) are deliberately excluded from these fixed-date tables, since a static date would go stale — they're treated as reference/awareness content elsewhere on the site instead.

Time zones. Time zone conversion uses the IANA Time Zone Database — the same database built into modern browsers and operating systems — via named regions (like America/New_York) that carry their full Daylight Saving Time rule history, rather than fixed numeric offsets that would silently become wrong across a DST transition.

Testing. The underlying date-math library ships with an automated test suite covering leap-year edge cases, month-end overflow, ISO week boundaries, and weekday computation across a wide date range, so a change to one tool's logic can't silently break another tool that shares the same engine.

Data freshness. Per-country public holiday tables are dated as of 2026-07-12 and reviewed on an annual refresh cadence, since public holiday rules do occasionally change by legislation.