You can determine which week we are now by checking the ISO week number, which counts weeks from Monday. For 2025, the current ISO week runs from Monday of that week through Sunday, and it resets to Week 1 on the Monday closest to January 1. The fastest check is a calendar app or the ISO 8601 formula, not a rough mental count from New Year's Day.
That answer sounds simple. The machinery behind it is not. Week numbering is a surprisingly contested piece of civil infrastructure, and getting it wrong creates real errors in payroll, medical records, project deadlines, and international scheduling. This explainer goes one level deeper than a calendar lookup: how week numbers are actually computed, why different systems disagree, where the edge cases bite, and how to find your week reliably every time.
The two competing week definitions
There are two dominant week-numbering systems in the world, and they do not agree. Understanding the difference explains most week confusion.
The ISO 8601 system, used across most of Europe and in international standards, defines Week 1 as the week containing the first Thursday of the year. Equivalently, it is the week that contains January 4. Weeks run Monday through Sunday. A year therefore has either 52 or 53 ISO weeks, and the first few days of January can belong to Week 52 or 53 of the previous year.
The other major system is the simple "week 1 starts January 1" convention, common in the United States, Canada, and many consumer calendars. In this system, Week 1 is the partial week containing January 1, and weeks reset on the same weekday January 1 falls on. This produces 53 or 54 partial weeks and differs from ISO numbering by one or two weeks for most of January and late December.
The mechanism behind the divergence is the anchoring rule. ISO anchors weeks to a weekday (Thursday) so that every week is a full seven days and the calendar year aligns with workweeks. The January 1 system anchors weeks to a date, accepting fragmented first and last weeks. Neither is more correct; they answer different questions. ISO answers "how many complete workweeks have passed." The January 1 system answers "how many days into the year am I, divided by seven."
How the ISO week number is actually calculated
The ISO week algorithm is deterministic and can be computed by hand, which means you never actually need to guess.
The standard identity: the ISO week number equals the week containing the year's first Thursday. A practical formula uses the "Thursday of the current week" trick. Take any date, find the Thursday of the week it belongs to, and that Thursday's year determines both the week-year and, through the day-of-year count, the week number.
The computation steps are stable:
Identify the Thursday of the week containing your target date by shifting the date forward or backward by the number of days between it and Thursday. Determine which calendar year that Thursday falls in. That year is the ISO week-year. Count the Thursdays from January 1 of that week-year through your Thursday. That count is the ISO week number.
A concrete example: January 1, 2025 falls on a Wednesday. The Thursday of that week is January 2, 2025. Because that Thursday is in 2025, the week containing January 1, 2025 is ISO Week 1 of 2025. By contrast, January 1, 2023 fell on a Sunday, so its week's Thursday was December 29, 2022, placing those New Year days in the final week of 2022.
The key insight: the week number is attached to the Thursday, not to the date. That is the counterintuitive detail many people miss. A date in early January can belong to the previous year's week 52 or 53, and a date in late December can belong to the next year's week 1.
Quantified context: how many weeks, and when they shift
Year to year, the number of ISO weeks varies between 52 and 53. A 53-week ISO year occurs when the year begins on a Thursday, or when it is a leap year beginning on a Wednesday. Roughly 71 of every 400 years carry 53 ISO weeks, so about one year in five or six. Recent 53-week ISO years include 2015, 2020, and 2026. That 2026 date matters for anyone scheduling more than a year ahead.
The week-year boundary shifts by one or two days each year because 365 days is 52 weeks plus one day, and 366 days is 52 weeks plus two days. Each ordinary year pushes the weekday of January 1 forward by one, and each leap year pushes it forward by two. Over a four-year cycle, the January 1 weekday advances by five positions, so the pattern of week alignment repeats on a 28-year solar cycle in the absence of century leap-year exceptions.
For "which week we are now," this means your answer changes slowly within a year but can jump at year boundaries. In a 53-week year, Week 53 exists and is real; ignoring it causes the final week of December to be mislabeled as Week 1 of the next year in many consumer calendars.
Timeline: a year's week structure in ISO terms
| Period | ISO week behavior | Practical note |
|---|---|---|
| Early January | Dates may belong to prior year's Week 52 or 53 | Check the Thursday's year, not the date's year |
| Mid-January onward | Week numbers align with calendar intuition | Most confusion has passed by mid-month |
| Late December | Dates may belong to next year's Week 1 | Holiday scheduling errors cluster here |
| 53-week years | Week 53 exists before the reset | Payroll and billing cycles need an extra period |
| Leap years | Boundary shifts by two days, not one | Schedules near January 1 drift faster |
| 28-year solar cycle | Weekday pattern repeats absent century rules | Long-range planning anchors here |
The table makes the core point visible: the risk window is narrow, concentrated in the first and last two weeks of the year. Mid-year, almost any week-numbering method agrees within one.
Edge cases that break naive counting
The naïve method, counting days since January 1 and dividing by seven, produces errors in three specific situations.
First, the partial first week. If January 1 falls midweek, dividing elapsed days by seven assigns the first few days to "Week 0" or "Week 1" inconsistently. ISO resolves this by assigning those days to the previous year's final week. The practical consequence is that ISO Week 1 sometimes starts in December.
Second, the 53-week year. A divisor-based method caps at 52 and either loses a week or double-counts one. Payroll systems that assume 52 weeks per year misalign period counts in 53-week years, which is why payroll calendars explicitly track week 53.
Third, time-zone leakage. Week boundaries are local-midnight events. A date computed in UTC can fall into a different ISO week than the same moment computed in local time, especially near midnight Sunday-to-Monday. Software that stores timestamps in UTC and derives week numbers without time-zone conversion produces off-by-one errors at week boundaries.
The professional caveat: week numbers are identifiers, not durations. Two dates "one week apart" in week-number terms may be eight days apart in real time if they straddle a year boundary. Never compute elapsed time from week numbers; compute it from dates.
Common misconceptions about week numbers
Several beliefs about weeks are widespread and wrong.
Misconception one: "Week 1 always starts January 1." It does not under ISO, and even under the January 1 system, Week 1 may be a partial week of one to six days.
Misconception two: "There are always 52 weeks in a year." There are 52 weeks plus one day in an ordinary year and 52 weeks plus two days in a leap year, which is exactly why 53-week ISO years exist.
Misconception three: "Week numbers are universal." They are not. The same date can be Week 2 in one system and Week 1 in another, and international teams routinely schedule against mismatched numbers without noticing.
Misconception four: "The week number on my phone is standardized." Consumer calendars vary by region and by app setting. Your phone may show the January 1 convention while your European colleague's shows ISO, and both are "correct" within their settings.
Practical actions to get your week right
Finding the current week reliably takes one deliberate step beyond a glance at a calendar.
Set your calendar app's week-number setting to ISO 8601 if you work across borders or with standards-based systems. The setting is usually labeled "ISO week numbers" or "week numbering." If you need the week number today, open the calendar and hover the current date, or use the Thursday-of-the-week rule: the week number belongs to the Thursday of that week. Record week numbers as "week-year" pairs, such as 2025-W14, never as bare numbers. A bare "Week 14" is ambiguous across systems and years. For payroll or billing, confirm whether your system uses 52-week or 53-week calendars before the year starts, especially ahead of 2026, which carries 53 ISO weeks. For software, convert timestamps to local time before deriving week numbers, and test the Sunday-to-Monday boundary explicitly. Never calculate elapsed days from week numbers; use date subtraction, which is unambiguous.
These steps are cheap and eliminate the most common errors. The threshold to adopt them is simply any recurring schedule that crosses a year boundary or an international team.
Limits of what week numbering can tell you
Week numbers are a coordination tool, not a measurement of time elapsed. They tell you where a date sits in a labeled grid; they do not tell you how many days have passed, how many workdays remain, or how long a project has run. For all of those, date arithmetic is the correct instrument.
The systems also cannot be "reconciled" into one universal answer, because they answer different questions. ISO week numbers measure complete workweeks. The January 1 convention measures elapsed calendar days in seven-day chunks. When someone asks "which week we are now," the honest answer depends on which question they are actually asking, and the reliable move is to state the convention alongside the number.
Finally, long-range week planning should account for the 53-week irregularity and the 28-year weekday cycle, not assume a fixed 52-week year. That single adjustment prevents the most consequential scheduling and payroll errors.