Skip to main content

ISO Week Number Calculator

Find the ISO 8601 week number for any date and the start/end dates of any week. Enter values for instant results with step-by-step formulas.

Skip to calculator
Date & Time

Iso Week Number Calculator

Find the ISO 8601 week number for any date and the start/end dates of any ISO week. Supports date-to-week and week-to-date conversions.

Last updated: December 2025

Calculator

Adjust values & calculate
ISO Week
W20
2026-W20-7
Week Starts
Mon, May 11, 2026
Week Ends
Sun, May 17, 2026
Day
Sunday
Day of Year
137
Quarter
Q2

Year Summary

ISO Year2026
Total ISO Weeks53
Weeks Remaining33
Days Remaining in Year228
Leap YearNo
Your Result
ISO 2026-W20-7 | Mon, May 11, 2026 to Sun, May 17, 2026
Share Your Result
Understand the Math

Formula

ISO Week 1 = week containing Jan 4th (first Thursday of January)

ISO 8601 defines week 1 as the week containing the first Thursday of January. Weeks start on Monday and end on Sunday. The ISO week-numbering year may differ from the calendar year at the boundaries.

Last reviewed: December 2025

Worked Examples

Example 1: Finding the ISO Week for a Date

What is the ISO week number for March 15, 2025?
Solution:
Date: March 15, 2025 (Saturday) Day of year: 31 + 28 + 15 = 74 Day of week (ISO): Saturday = 6 Thursday of same week: March 13, 2025 (day 72) Week number: ceil(72 / 7) = ceil(10.29) = 11 ISO notation: 2025-W11-6
Result: ISO Week 11, 2025 | 2025-W11-6 | Week: Mon Mar 10 - Sun Mar 16, 2025

Example 2: Year-Boundary ISO Week

What ISO week does January 1, 2023 belong to?
Solution:
January 1, 2023 falls on a Sunday ISO day of week: Sunday = 7 Thursday of same week: December 29, 2022 This Thursday is in 2022, so this week belongs to 2022 ISO Week 52 of 2022 ISO notation: 2022-W52-7
Result: 2022-W52-7 | January 1, 2023 belongs to ISO Week 52 of 2022 (not 2023!)
Expert Insights

Background & Theory

The Iso Week Number Calculator applies the following established principles and formulas. Date and time calculations underpin a vast range of applications from financial settlement to scheduling and age verification. The complexity arises because civil timekeeping uses irregular units: months have 28, 29, 30, or 31 days; years have 365 or 366 days; hours, minutes, and seconds use base-60 arithmetic; and time zones introduce offsets ranging from -12:00 to +14:00 relative to UTC. The Gregorian calendar's leap year rule is a compound condition: a year is a leap year if it is divisible by 4, except for century years, which must be divisible by 400. Thus 1900 was not a leap year but 2000 was. This rule keeps the calendar synchronized with the solar year to within about 26 seconds per year. For algorithmic date calculations, the Julian Day Number provides a continuous integer count of days since January 1, 4713 BCE, eliminating the irregularity of calendar months and making interval arithmetic straightforward. The Unix epoch, by contrast, counts seconds since 00:00:00 UTC on January 1, 1970, and is the basis of POSIX time used in most computing systems. ISO 8601 standardizes date and time representation as YYYY-MM-DD and combined datetime as YYYY-MM-DDTHH:MM:SSยฑHH:MM, ensuring unambiguous machine-readable interchange across locales that would otherwise differ in day/month/year ordering. Business day calculation requires excluding weekends and, optionally, a jurisdiction-specific list of public holidays. Duration calculations expressed in years, months, and days must account for the variable length of months, making them non-commutative: the interval from January 31 to February 28 is different from the interval from February 28 to March 31. Age calculation algorithms must handle the edge case of birthdays on February 29 and ensure that a person born on December 31 is not counted as one year older on January 1 of the following year until the clock passes midnight. Zeller's Congruence provides a closed-form formula to determine the day of the week for any Gregorian or Julian calendar date using only integer arithmetic.

History

The history behind the Iso Week Number Calculator traces back through the following developments. The need to track time and predict astronomical events gave rise to calendrical systems independently across many civilizations. The Babylonians, around 2000 BCE, developed a lunisolar calendar with 12 months of alternating 29 and 30 days, inserting an intercalary month periodically to keep pace with the solar year. They also divided the day into 24 hours and the hour into 60 minutes, a sexagesimal convention that persists in every modern clock. The Egyptian civil calendar used 12 months of exactly 30 days plus five epagomenal days, totaling 365 days. Though simple for administrative purposes, it drifted against the solar year by one day every four years. Julius Caesar, advised by the Egyptian astronomer Sosigenes, reformed the Roman calendar in 45 BCE. The Julian calendar introduced a 365-day year with a leap day every four years, a system that served Europe for over sixteen centuries. By the 16th century, the accumulated error of the Julian calendar had shifted the spring equinox ten days from its ecclesiastically mandated date, disrupting the calculation of Easter. Pope Gregory XIII commissioned the calendar reform that bears his name, and the Gregorian calendar was introduced in Catholic countries in October 1582. The transition required skipping ten days: October 4 was followed by October 15. Protestant and Orthodox countries adopted the reform slowly; Britain and its colonies switched in 1752, Russia not until 1918, and Greece in 1923. The expansion of railways in the 1840s created an urgent practical problem: each city operated on its own local solar time, making train timetables impossible to coordinate. British railways adopted Greenwich Mean Time as a standard in 1847. The International Meridian Conference of 1884 in Washington formalized the prime meridian at Greenwich and established the global framework of 24 time zones. Daylight saving time was first adopted nationally during World War I to reduce coal consumption. The development of atomic clocks after World War II led to the definition of Coordinated Universal Time (UTC) in 1960, accurate to nanoseconds. The Y2K problem of 1999-2000 demonstrated that two-digit year storage in legacy systems could cause widespread failures, prompting a global remediation effort costing an estimated 300 to 600 billion dollars.

Share this calculator

Explore More

Frequently Asked Questions

The ISO 8601 week numbering system is an international standard for representing dates using week numbers instead of traditional month-day formats. In this system, weeks always start on Monday and end on Sunday. Week 1 of any year is defined as the week that contains the first Thursday of January, which equivalently means it is the week containing January 4th. This definition ensures that week 1 always contains the majority of its days in the new year. An ISO week date is written as YYYY-Www-D, where YYYY is the ISO week-numbering year, ww is the week number (01 to 52 or 53), and D is the day number (1 for Monday through 7 for Sunday). Most years have 52 weeks, but some long years have 53 weeks.
Most years have exactly 52 ISO weeks, but some years have 53 weeks. This occurs because a calendar year has 365 days (or 366 in leap years), which is one or two days more than 52 complete weeks (364 days). A year has 53 ISO weeks when January 1st falls on a Thursday in a common year, or when January 1st falls on a Wednesday or Thursday in a leap year. In practical terms, this happens roughly every 5 to 7 years. For example, the years 2004, 2009, 2015, 2020, and 2026 all have 53 ISO weeks. The extra week (week 53) occurs at the end of December when those final days belong to the current ISO year rather than week 1 of the next year. This pattern ensures consistent week numbering across year boundaries.
The ISO week-numbering year can differ from the calendar year at the boundaries of the year. Since ISO week 1 is defined as the week containing the first Thursday of January, the first few days of January might belong to the last ISO week of the previous year, and conversely, the last few days of December might belong to ISO week 1 of the following year. For example, December 31, 2020 was actually in ISO week 53 of 2020, but January 1, 2021 was in ISO week 53 of 2020 as well (since that week started on December 28, 2020). This discrepancy occurs because ISO weeks never span across week boundaries. When working with ISO week dates, always use the ISO year rather than the calendar year to avoid off-by-one errors.
ISO week numbers are widely used across industries and countries worldwide. In Europe, ISO week numbering is the standard for business planning, financial reporting, and scheduling. Many European countries display week numbers on their calendars by default. In manufacturing and supply chain management, production schedules and delivery timelines are often referenced by week number rather than specific dates. Software development teams using Agile methodology frequently plan sprints and releases using ISO week numbers. Epidemiologists and public health organizations report disease surveillance data by ISO week. Broadcasting and media companies schedule programming using week numbers. Tax authorities in several countries use ISO weeks for reporting periods. Most modern programming languages and databases support ISO week calculations natively.
To calculate the ISO week number manually, follow these steps. First, find the ordinal day of the year (January 1 = 1, February 1 = 32, etc.). Then determine the day of the week using Zeller's congruence or a reference calendar, where Monday equals 1 and Sunday equals 7. Next, calculate the Thursday of the same week by adding (4 minus the day-of-week) to the ordinal day. The ISO week number is then the Thursday's ordinal day divided by 7, rounded up. For dates near year boundaries, you must check whether the result belongs to the previous year (if it falls before week 1 starts) or the next year (if December dates belong to week 1 of the following year). This manual process is error-prone at year boundaries, so using a calculator or programming function is recommended for accuracy.
ISO 8601 formats dates as YYYY-MM-DD (e.g., 2025-03-15), eliminating ambiguity between US (MM/DD/YYYY) and European (DD/MM/YYYY) formats. It sorts chronologically as text, is internationally recognized, and is the standard for data exchange and APIs.
Educational Note: This calculator is provided for educational and informational purposes. Results are based on the formulas and inputs provided. Always verify important calculations independently. NovaCalculator processes calculator inputs client-side; optional analytics follow visitor consent settings. ยฉ 2024โ€“2026 NovaCalculator.

Share this calculator

Formula

ISO Week 1 = week containing Jan 4th (first Thursday of January)

ISO 8601 defines week 1 as the week containing the first Thursday of January. Weeks start on Monday and end on Sunday. The ISO week-numbering year may differ from the calendar year at the boundaries.

Worked Examples

Example 1: Finding the ISO Week for a Date

Problem: What is the ISO week number for March 15, 2025?

Solution: Date: March 15, 2025 (Saturday)\nDay of year: 31 + 28 + 15 = 74\nDay of week (ISO): Saturday = 6\nThursday of same week: March 13, 2025 (day 72)\nWeek number: ceil(72 / 7) = ceil(10.29) = 11\nISO notation: 2025-W11-6

Result: ISO Week 11, 2025 | 2025-W11-6 | Week: Mon Mar 10 - Sun Mar 16, 2025

Example 2: Year-Boundary ISO Week

Problem: What ISO week does January 1, 2023 belong to?

Solution: January 1, 2023 falls on a Sunday\nISO day of week: Sunday = 7\nThursday of same week: December 29, 2022\nThis Thursday is in 2022, so this week belongs to 2022\nISO Week 52 of 2022\nISO notation: 2022-W52-7

Result: 2022-W52-7 | January 1, 2023 belongs to ISO Week 52 of 2022 (not 2023!)

Frequently Asked Questions

What is the ISO 8601 week numbering system?

The ISO 8601 week numbering system is an international standard for representing dates using week numbers instead of traditional month-day formats. In this system, weeks always start on Monday and end on Sunday. Week 1 of any year is defined as the week that contains the first Thursday of January, which equivalently means it is the week containing January 4th. This definition ensures that week 1 always contains the majority of its days in the new year. An ISO week date is written as YYYY-Www-D, where YYYY is the ISO week-numbering year, ww is the week number (01 to 52 or 53), and D is the day number (1 for Monday through 7 for Sunday). Most years have 52 weeks, but some long years have 53 weeks.

Why do some years have 53 ISO weeks?

Most years have exactly 52 ISO weeks, but some years have 53 weeks. This occurs because a calendar year has 365 days (or 366 in leap years), which is one or two days more than 52 complete weeks (364 days). A year has 53 ISO weeks when January 1st falls on a Thursday in a common year, or when January 1st falls on a Wednesday or Thursday in a leap year. In practical terms, this happens roughly every 5 to 7 years. For example, the years 2004, 2009, 2015, 2020, and 2026 all have 53 ISO weeks. The extra week (week 53) occurs at the end of December when those final days belong to the current ISO year rather than week 1 of the next year. This pattern ensures consistent week numbering across year boundaries.

How does the ISO week year differ from the calendar year?

The ISO week-numbering year can differ from the calendar year at the boundaries of the year. Since ISO week 1 is defined as the week containing the first Thursday of January, the first few days of January might belong to the last ISO week of the previous year, and conversely, the last few days of December might belong to ISO week 1 of the following year. For example, December 31, 2020 was actually in ISO week 53 of 2020, but January 1, 2021 was in ISO week 53 of 2020 as well (since that week started on December 28, 2020). This discrepancy occurs because ISO weeks never span across week boundaries. When working with ISO week dates, always use the ISO year rather than the calendar year to avoid off-by-one errors.

Where are ISO week numbers commonly used?

ISO week numbers are widely used across industries and countries worldwide. In Europe, ISO week numbering is the standard for business planning, financial reporting, and scheduling. Many European countries display week numbers on their calendars by default. In manufacturing and supply chain management, production schedules and delivery timelines are often referenced by week number rather than specific dates. Software development teams using Agile methodology frequently plan sprints and releases using ISO week numbers. Epidemiologists and public health organizations report disease surveillance data by ISO week. Broadcasting and media companies schedule programming using week numbers. Tax authorities in several countries use ISO weeks for reporting periods. Most modern programming languages and databases support ISO week calculations natively.

How do I calculate the ISO week number manually?

To calculate the ISO week number manually, follow these steps. First, find the ordinal day of the year (January 1 = 1, February 1 = 32, etc.). Then determine the day of the week using Zeller's congruence or a reference calendar, where Monday equals 1 and Sunday equals 7. Next, calculate the Thursday of the same week by adding (4 minus the day-of-week) to the ordinal day. The ISO week number is then the Thursday's ordinal day divided by 7, rounded up. For dates near year boundaries, you must check whether the result belongs to the previous year (if it falls before week 1 starts) or the next year (if December dates belong to week 1 of the following year). This manual process is error-prone at year boundaries, so using a calculator or programming function is recommended for accuracy.

What is ISO 8601 and why should I use it for dates?

ISO 8601 formats dates as YYYY-MM-DD (e.g., 2025-03-15), eliminating ambiguity between US (MM/DD/YYYY) and European (DD/MM/YYYY) formats. It sorts chronologically as text, is internationally recognized, and is the standard for data exchange and APIs.

References

Reviewed by Abdullah, Technical Content Specialist ยท Editorial policy