Skip to content

Weekday Calculator

Find the weekday, ordinal day, remaining days, quarter, and leap/common year type for an exact Gregorian date without time-zone date shifting.

Use this result well

Inputs that matter
One strict YYYY-MM-DD Gregorian calendar date from 1600-01-01 through 9999-12-31
Output to expect
Weekday, preserved ISO and long date, ordinal day, days remaining, quarter and leap/common year type
How it works
Derives calendar position on a UTC-stable whole-day axis while preserving the entered year/month/day fields exactly
  • Reconcile the repeated ISO date before using the weekday; a date-only result does not identify a time zone, instant, business day or holiday.
  • For historical records, confirm the source calendar and local adoption date; this tool applies the Gregorian rule uniformly across its supported range.

Choose your path

Built around the job you need to finish

Inspect the weekday, ordinal day, remaining days, quarter and year type for one preserved Gregorian date without a UTC-to-local one-day shift.

Scheduler checking one historical or future date

Know the weekday for the exact date written in a record.

Enter the ISO date and reconcile the returned ISO/long date before using the weekday.

The output repeats the same date fields and the correct weekday.

Analyst using ordinal dates

Verify day-of-year and remaining-day position around leap years.

Test dates before, on and after February 29 and inspect year type.

Ordinal counts follow the Gregorian leap rule without a local-zone shift.

New York user reproducing the old defect

Prevent 2026-07-17 from becoming 2026-07-16 Thursday.

Run the authored Friday example and inspect exact date, weekday and day 198.

Gets Friday for the entered July 17 date with no contradictory interpretation.

Was this tool helpful?

Reference & details

How it works

Preserved Calendar Fields

The input is parsed as exact Gregorian year, month, and day fields. Impossible dates and values outside 1600-01-01 through 9999-12-31 are rejected.

UTC-Stable Weekday Axis

The validated calendar fields are placed on a whole-day axis for weekday and ordinal arithmetic; local time getters are never mixed with UTC parsing.

Weekday = Gregorian serial day modulo seven

Ordinal and Leap Context

Day-of-year and remaining-day counts use the Gregorian 4/100/400 leap-year rule. Quarter is a calendar grouping, not a fiscal-calendar inference.

Updated: August 2026

Example Scenarios

A coordinator checks an exact milestone date, verifies the repeated ISO date, and records its weekday without treating it as a workday.

An analyst checks February 29 and a later date to confirm the expected ordinal-day shift in a leap year.

A New York user enters 2026-07-17 and confirms the result remains Friday, July 17 rather than shifting to Thursday, July 16.

Common Mistakes to Avoid

Parsing YYYY-MM-DD as UTC and then reading it with local date getters

Preserve the entered calendar fields and use one UTC-stable whole-day basis for all weekday and ordinal calculations.

Assuming a named weekday is automatically a business day or valid historical-calendar classification

Check work schedules, holidays, fiscal conventions, and the source calendar or adoption context separately.

FAQ

Repeating YYYY-MM-DD lets you verify that the engine classified the date you entered rather than a UTC instant shifted into a different local day.

Yes. The authored regression example returns Friday and ordinal day 198 for 2026-07-17.

January 1 is day 1. Dates after February 28 are one ordinal day higher in Gregorian leap years because February contains 29 days.

No. The result names the calendar weekday only. It does not apply work schedules, public holidays, closures, or locale-specific weekend rules.

The engine applies Gregorian rules uniformly from 1600 onward. Confirm the calendar and adoption context of the original source before classifying historical records.

About Weekday Calculator

Inspect one exact YYYY-MM-DD Gregorian date. The engine repeats the preserved ISO date alongside its weekday and ordinal position so a local UTC offset cannot silently move the record to the previous day.