Day of the Week Calculator

Knowing what day of the week a specific date falls on matters more than you'd think. Legal deadlines expire on certain weekdays. Contracts specify that payments are due on the first Monday of the month. Someone wants to know what day of the week they were born. A genealogist is verifying historical records by checking whether a reported date matches the claimed weekday. A simple question — "what day was March 15th, 1953?" — requires either a calendar from that year or an algorithm.

Historical and Genealogical Applications

Genealogists frequently encounter weekday-date consistency checks. A marriage certificate recording a Saturday wedding is plausible. A recorded wedding on a Tuesday is also plausible, though less common. But a certificate claiming a marriage on a Sunday in a deeply religious community during the 1800s warrants scrutiny — Sunday weddings were uncommon in many religious traditions of that era.

Historical event verification sometimes requires day-of-week calculation. The signing of the Declaration of Independence on July 4, 1776 — was it a Thursday? Yes. The Titanic struck the iceberg on April 14, 1912 — Sunday night / Monday morning. John F. Kennedy was assassinated on November 22, 1963 — a Friday. The Battle of Waterloo was June 18, 1815 — Sunday. Historical accounts that describe these events referencing the day of the week can be verified against the actual weekday.

Family histories and oral traditions sometimes preserve weekday information ("Grandma was born on a Tuesday") without specifying dates. Cross-referencing known birth years with approximate birth dates can narrow down possibilities when only the weekday is remembered. If someone born in 1932 was told they were born on a Tuesday in mid-July, checking which Tuesdays fell in July 1932 narrows the possibilities to approximately 4 or 5 candidate dates.

Related Calculators

• Birthday Calculator
• Date Difference Calculator
• Business Days Calculator

Why Day-of-Week Calculation Matters

Most of the time, you need the day of the week for a date you can look up on a current calendar. But for historical dates, future dates far out, or dates in historical contexts (was Julius Caesar assassinated on an Ides that was actually a Wednesday?), the calculation becomes interesting and useful.

Legal and business contexts generate the most practical need. Lease agreements often specify rent due on the first business day of the month. A contract might say "30 days from signing," and you need to know if day 30 falls on a weekend (in which case the deadline may extend to the next business day). Court filing deadlines computed as "5 business days from notice" require knowing which days are actual business days.

The Gregorian calendar, in use since 1582 and now universal, repeats its day-of-week pattern every 400 years. Within that 400-year cycle, the calendar cycles through day/date combinations in a predictable mathematical pattern. This predictability is what makes algorithmic day-of-week calculation possible.

Calendar Reform and the Julian Calendar

The Gregorian calendar replaced the Julian calendar in October 1582 in Catholic countries, and progressively later in Protestant and Eastern Orthodox countries — Britain and its colonies didn't switch until 1752; Russia not until 1918. Historical dates before these transitions were recorded in the Julian calendar, which differs from the Gregorian by an accumulated date offset that grows over centuries.

The Julian calendar doesn't have the same 400-year leap year rule as the Gregorian — it simply adds a leap year every 4 years without exceptions. This means it falls behind the Gregorian calendar by 3 days every 400 years. By 1582, the Julian calendar was 10 days behind the Gregorian. By 1752 (when Britain switched), it was 11 days behind.

This matters for day-of-week calculations when working with historical European dates before the switch. A date recorded in Julian calendar terms ("March 1, 1600 O.S." — "Old Style") corresponds to a different Gregorian date and a different weekday. Genealogists and historians working with pre-Gregorian records routinely encounter "Old Style / New Style" date discrepancies and need to understand how they affect day-of-week calculations.

Recurring Weekday Calculations

Many scheduling scenarios involve recurring weekday patterns. "Every second Tuesday" or "the first Monday of each month" requires systematic calculation to identify specific upcoming dates. If a board meeting is scheduled for the third Thursday of each quarter, what are the next 8 meeting dates from today?

The pattern for "nth weekday of month": determine what day of the week the first of the month falls on, then count forward to the desired weekday. If the first is a Wednesday and you want the second Monday: Monday is 5 days after Wednesday (Wednesday → Thursday +1 → Friday +2 → Saturday +3 → Sunday +4 → Monday +5), so the first Monday is the 6th. The second Monday is the 13th. The third is the 20th. The fourth is the 27th. If the month has only 28 days and the fourth Monday is the 27th, there is no fifth Monday that month.

Time zone considerations affect recurring weekday calculations for international events. A meeting set for "every Monday at 9 AM Pacific" occurs at different UTC times during Pacific Standard Time (UTC-8) and Pacific Daylight Time (UTC-7). International attendees experience this as the meeting shifting by one hour for the portions of the year when time zones are offset due to DST differences.

How Day-of-Week Algorithms Work

The most accessible algorithm is Zeller's congruence, published by Christian Zeller in 1887. For the Gregorian calendar: h = (q + ⌊13(m+1)/5⌋ + K + ⌊K/4⌋ + ⌊J/4⌋ - 2J) mod 7, where q is the day of month, m is the month number (January and February are counted as months 13 and 14 of the previous year), K is the year within the century (year mod 100), J is the zero-based century, and h is the day (0=Saturday, 1=Sunday, 2=Monday, ..., 6=Friday).

Simpler to understand is the Doomsday algorithm, invented by mathematician John Conway. The key insight: certain "anchor dates" always fall on the same day of the week for a given year. For any year, calculate the "Doomsday" for that year (the day that 4/4, 6/6, 8/8, 10/10, 12/12, the last day of February, and several other memorable dates all share). Then count from the nearest anchor date to your target date to find the day.

These algorithms are fascinating mathematically, but for practical purposes, a calculator handles the computation instantly. The valuable skill isn't mental arithmetic — it's knowing when you need the answer and trusting the tool to deliver it accurately.

Days Between Dates and Business Day Counting

Related to day-of-week calculation is the question of how many days — specifically how many business days — exist between two dates. This matters for SLA compliance, payment terms, and legal deadlines.

Business day calculation requires accounting for weekends and, optionally, specific holidays. The naive calculation (total days minus 2 for each weekend) works for spans that don't start or end on a weekend, but edge cases multiply quickly. Does the start date count? Does the end date count? What if the start is Friday and the end is Monday — 1 business day or 2?

For legal and financial purposes, conventions vary. "Net 30" payment terms in business typically means 30 calendar days from invoice date, with the due date moving to the next business day if it falls on a weekend or holiday. "5 business days" for court filings means 5 weekdays excluding federal holidays, with the counting starting the day after notice was received.