Finding a weekday from a date
Every valid calendar date falls on one of seven weekdays. The cycle continues without resetting at the end of a month or year, so a weekday can be calculated by mapping the date to a continuous day count and taking the remainder after division by seven.
Month lengths and leap years make the mapping less obvious than counting forward on a wall calendar. A reliable algorithm applies the calendar rules consistently, including century exceptions, and states which calendar it uses.
This calculator uses the proleptic Gregorian calendar: the modern Gregorian rules are extended backward even for dates before a country historically adopted them. It treats the input as a calendar date, not as a moment in a local time zone.
Gregorian leap-year rules
A common year contains 365 days, which is 52 full weeks plus one day. Therefore a given date normally moves forward one weekday in the next year. A leap year contains 366 days and moves it forward two weekdays for dates after February.
The Gregorian rule is:
divisible by 4: leap year
divisible by 100: not a leap year
divisible by 400: leap year after all
The year 2024 is divisible by four and is a leap year. The year 1900 is divisible by 100 but not 400, so it was a common year. The year 2000 is divisible by 400 and was a leap year.
These exceptions keep the calendar aligned more closely with the solar year than a simple every-four-years rule.
ISO weekday numbering
Weekday names depend on language, but ISO 8601 provides a numeric convention that is easy to exchange between systems:
Monday 1
Tuesday 2
Wednesday 3
Thursday 4
Friday 5
Saturday 6
Sunday 7
Other systems use different numbering. JavaScript’s traditional date API uses Sunday as 0 through Saturday as 6. Some calendars display Sunday as the first column, while many countries display Monday first. A stored number is ambiguous unless the convention is documented.
The calculator reports the ISO number and presents the weekday name using the browser’s locale where supported.
ISO weeks and week years
ISO weeks begin on Monday and contain seven complete days. ISO week 1 is the week containing the first Thursday of the year. The same rule can be stated as the week containing January 4.
This means the ISO week-numbering year does not always match the calendar year near New Year. January 1, 2, or 3 can belong to the final ISO week of the previous year. December 29, 30, or 31 can belong to ISO week 1 of the following year.
For example, Friday 1 January 2021 belonged to ISO week 53 of 2020. The label “2021-W53” would be wrong even though the calendar date’s year was 2021. Always carry the ISO week year alongside the week number.
Day of year
The ordinal day counts January 1 as day 1 and continues through the year. December 31 is day 365 in a common year and day 366 in a leap year.
Before March, the same month and day have the same ordinal position in leap and common years. From March onward, a leap year’s extra February day shifts the ordinal by one. March 1 is day 60 in a common year and day 61 in a leap year.
Ordinal dates are useful in logs, manufacturing, scientific datasets, and schedules, but the year must always accompany the number because “day 120” alone repeats annually.
Worked examples
23 August 2026 falls on a Sunday. Under ISO numbering Sunday is day 7. It is day 235 of a common year and belongs to ISO week 34 of 2026.
29 February 2024 falls on a Thursday. It is the 60th day of the leap year. The next day, 1 March, is day 61. In a common year, 1 March is day 60 because February contains only 28 days.
1 January 2000 falls on a Saturday. Although it begins calendar year 2000, it belongs to ISO week 52 of 1999 because the week’s Thursday was still in December 1999. The year 2000 was a leap year under the divisible-by-400 exception.
4 October 1582 evaluates under the proleptic Gregorian rules in this tool. A historical document from a place still using the Julian calendar could label or interpret that date differently.
Why time zones are excluded
A date such as 2026-08-23 has no time of day or location. It names a calendar day directly. Converting it through local midnight can create bugs: the equivalent instant may still be the previous date in another zone, and daylight-saving transitions can make local durations unusual.
The calculator constructs and compares dates in Coordinated Universal Time to preserve the entered year, month, and day. UTC is used as a stable arithmetic frame; it does not imply that the historical or future event occurred in UTC.
If the input is an instant—such as 2026-08-23T23:30Z—the weekday depends on the target time zone. That instant is already Monday in locations more than 30 minutes ahead of UTC. Use a time-zone converter for that question.
Historical calendar adoption
Pope Gregory XIII introduced the Gregorian reform in 1582, but adoption differed across countries and territories. Some changed quickly; others continued with the Julian calendar for decades or centuries. Transitions skipped dates to realign the calendar with the seasons.
As a result, a historical statement like “the weekday of 10 February 1700” can require a place and calendar. The date may have been Julian in one country and Gregorian in another. Extending Gregorian rules backward is convenient for consistent computation but does not reconstruct local civil practice.
Genealogy, archival research, legal history, and astronomy may use explicit Old Style and New Style notation. Consult a source for the relevant jurisdiction rather than treating a modern calendar result as historical proof.
Mental shortcuts
Because 365 leaves a remainder of one after division by seven, the same date advances one weekday in the following common year. Passing a leap day adds another shift for dates after February.
Within a year, months separated by a multiple of seven days begin on the same weekday. In a common year, February and March begin on the same weekday because February has exactly 28 days. January and October also share a starting weekday in a common year.
These patterns are useful checks but are easy to misapply around February or century years. A formal algorithm remains safer for distant dates.
Calendar algorithms
Several established algorithms calculate weekdays, including Zeller’s congruence and day-count methods based on a known epoch. They rearrange the same underlying facts: regular month lengths, leap corrections, century corrections, and a remainder modulo seven.
A day-count implementation converts a civil date into days from an epoch. If the epoch weekday is known, adding the day difference and taking modulo seven yields the target weekday. ISO week calculation then shifts to the week’s Thursday, which uniquely determines the ISO week year.
Different implementations can still disagree when they parse ambiguous text, use local time unintentionally, permit invalid dates to overflow into another month, or apply the Julian calendar. This calculator accepts the unambiguous year-month-day value from a date control and verifies the constructed date.
Weekends are not universal work rules
The result labels Saturday and Sunday as weekend because that is the widespread civil convention reflected by ISO’s Monday-to-Sunday week. Actual rest days and business days vary by country, religion, industry, and employer.
Some jurisdictions use Friday and Saturday weekends, some have changed their weekend historically, and essential services operate every day. A weekday result does not establish whether banks, markets, schools, or government offices were open.
For scheduling and deadlines, use a business-day calculator with the correct local holiday list and organizational rules.
Limits of the result
The weekday, ISO number, ISO week, and ordinal day are deterministic for a valid date under the stated Gregorian rules. The result does not account for local historical adoption, cultural calendar systems, religious calendars, or a specific time zone.
Dates far in the past may also be interpreted differently by source material. Years before the common era require an explicit year-numbering convention and are outside the date input used here.
Use the tool for modern scheduling, date checking, software testing, and proleptic Gregorian arithmetic. Use jurisdiction-specific historical sources when a calendar transition or legal date matters.