What Week Number Is It? ISO 8601 Weeks Explained
Find what week of the year any date falls in, learn the ISO 8601 rule that week 1 holds the year's first Thursday, and use week numbers for cleaner business scheduling.
What Week Number Is It? ISO 8601 Weeks Explained
Somebody on the team says "let's ship in W37" and half the room nods while the other half quietly opens a calendar to figure out what that actually means. Week numbers are a wonderful shorthand for planning, but only if everyone agrees on how the weeks are counted. They don't always. The number you read off a North-American spreadsheet and the number your European ERP system prints can disagree in the first days of January, and that one-week gap is enough to send a report to the wrong fortnight.
This post walks through how week numbering works under ISO 8601, why the first week of the year is defined by a Thursday of all things, and how to use week numbers without tripping over the edge cases. If you'd rather just read the answer for a specific date, the Week Number Calculator shows both the ISO and US numbers side by side.
The rule that runs everything: week 1 holds the first Thursday
ISO 8601 defines a week as starting on Monday and ending on Sunday. That part is easy. The interesting part is which week earns the title "week 1."
The rule is precise: ISO week 1 is the week that contains the year's first Thursday. An equivalent way to say it is that week 1 is the week containing January 4 — January 4 always lands in week 1, no matter what day of the week it is. A third equivalent: week 1 is the first week with the majority of its days (four or more) in the new year.
Why Thursday? Because Thursday is the midpoint of a Monday-to-Sunday week. Anchoring on it means a week belongs to whichever year holds most of its days. If January 1 lands on a Friday, that week has only Friday, Saturday, and Sunday in the new year — three days, a minority — so it stays attached to the previous year, and week 1 begins the following Monday. If January 1 lands on a Monday through Thursday, the new year already owns four or more days of that week, so it becomes week 1. The Thursday test captures this majority rule in a single check you can do in your head.
A worked example: pin a real date to its week
Let me run a concrete one. Take Wednesday, September 10, 2025, and find its ISO week number.
Start from a known anchor. January 1, 2025 was a Wednesday. Walk back to the Monday of that week — December 30, 2024 — and check the Thursday of that week, January 2, 2025. That Thursday is in 2025, so this week qualifies as ISO week 1 of 2025, running Monday December 30, 2024 through Sunday January 5, 2025.
Now count forward. From the Monday of week 1 (December 30, 2024) to the Monday on or before September 10, 2025, the elapsed time is 36 full weeks. Week 1 starts at day zero, so 36 weeks later is week 37. September 10, 2025 falls in ISO week 37 of 2025 — the same "W37" the marketing team was talking about. The calculator confirms it instantly, and it's a good habit to verify a hand count against the tool the first time you trust a new anchor date.
When the calendar year and the week-year disagree
Here's the trap that catches BI dashboards every few years: the year a week belongs to is not always the calendar year on the date.
Because an ISO week belongs to whichever year holds its Thursday, the first days of January can still belong to the previous year's final week, and the last days of December can belong to the next year's week 1. Two real cases:
- January 1, 2021 was a Friday. Its week's Thursday (December 31, 2020) sits in 2020, so January 1, 2021 is ISO week 53 of 2020, not week 1 of 2021.
- December 30, 2024 was a Monday. Its week's Thursday (January 2, 2025) sits in 2025, so December 30, 2024 is ISO week 1 of 2025.
The lesson: when a date is within a few days of January 1, read the week-year and not just the calendar year. A weekly sales total filed under "week 53, 2020" that your code stamps with the literal year 2021 will land in the wrong bucket, and you'll spend an afternoon hunting a phantom 53-week gap.
Why some years have 53 weeks
A common year is 365 days, which is 52 weeks plus one leftover day; a leap year adds a second leftover. Those spare days accumulate, and every five or six years the math forces a 53rd ISO week into the calendar.
The precise condition: a year has 53 ISO weeks when January 1 falls on a Thursday, or when it's a leap year and January 1 falls on a Wednesday. By that rule, 2015, 2020, and 2026 are 53-week years, while 2021 and 2025 have 52. This matters more than it looks. Annual planning templates that hardcode 52 rows silently drop the 53rd week's data, and a year-end close is the worst possible time to discover the bug. Check the total for the target year before you clone last year's spreadsheet — the calculator prints "weeks this year" right alongside the result.
Putting week numbers to work in scheduling
Once the counting is settled, week numbers become a clean planning unit. A few patterns that hold up:
- Name sprints by their week. "W22–W23" tells a developer in Berlin and a PM in São Paulo exactly which fortnight you mean, with no timezone argument and no ambiguous "next two weeks." Most Jira and Linear setups and European calendars already speak ISO, so the labels travel.
- Key reports to weeks, then expand to dates on demand. A finance report tagged "Week 6, FY2026" is compact, but reconciling it to bank statements needs real dates. Reverse the lookup — year plus week number gives you the Monday-to-Sunday span — and you've got the range to match against.
- Schedule biweekly jobs. Cron has no native "every other week," but "run only on even ISO weeks" is a one-line guard once you can compute the week number for any date.
- Mind the workdays inside the week. A week number tells you which seven-day block you're in, but holidays and weekends decide how much working time it actually contains. For deadline math I pair the week view with a business days calculator so a "due in W40" commitment reflects real capacity, not just calendar slots.
A note from my own use: I started leaning on week numbers when a recurring report kept landing a week off between our US spreadsheet and a partner's European system. The fix wasn't clever code — it was agreeing out loud that "week N" meant the ISO definition, then checking every disputed date against the same tool so nobody was arguing from a different rulebook. The disagreements stopped the day we shared one source of truth.
The short version
ISO week 1 is the week containing the year's first Thursday (equivalently, the week with January 4). Weeks run Monday to Sunday, a week belongs to the year that holds its Thursday, and that's why early-January dates can sit in week 52 or 53 of the prior year. Some years carry a 53rd week, so never hardcode 52. Get those three facts right and week numbers turn into one of the tidiest scheduling shorthands you have — match a counterpart's system before you quote a number, and let the Week Number Calculator handle the arithmetic.
Made by Toolora · Updated 2026-06-13