Practical guide
The 20th Monday of a Year vs Monday in Week 20
BYDAY=20MO counts the twentieth Monday within the year when no month or week-number selector is present. BYWEEKNO=20;BYDAY=MO selects Monday in week 20 under its week rules. These dates differ in 2026 even though they happen to agree in 2027 and 2028.
Choose a weekday ordinal or a week-number label
“The twentieth Monday of the year” numbers actual Mondays from the year’s first Monday. “Monday in week 20” uses a week-number system whose first week can begin near the year boundary. The labels can look interchangeable in one year and separate in another.
For this YEARLY comparison, BYDAY=20MO has neither BYMONTH nor BYWEEKNO. The numeric weekday therefore refers to the twentieth Monday in the year. The alternative BYWEEKNO=20;BYDAY=MO;WKST=MO selects Monday in numbered week 20. [1]
Keep these scopes explicit. Numeric BYDAY has other rules when month selectors are present, and RFC 5545 prohibits numeric YEARLY BYDAY when BYWEEKNO is specified. Do not combine 20MO with BYWEEKNO=20 in an attempt to reinforce the number.
Count the 2026 dates by both definitions
January 1 2026 is Thursday. The first Monday within the calendar year is January 5. Counting Mondays gives January 5 as 1, January 12 as 2, and May 18 as 20.
For a Monday-start week numbering system with the first week containing at least four days of that year, week 1 of 2026 starts on December 29 2025. Week 20 therefore starts on Monday May 11. RFC 5545 describes BYWEEKNO with the four-day first-week rule and gives WKST a role in this calculation. [1]
The one-week difference comes from counting Mondays inside the calendar year versus counting labeled weeks that can start outside it. Neither definition establishes an organization’s fiscal reporting week or academic term week. Those require their own calendar.
Verify a year where the results diverge
On a narrow screen, swipe within this table to read the remaining columns.
| Year | 20th Monday within year | Monday in week 20 | Relationship |
|---|---|---|---|
| 2026 | 18 May | 11 May | Different by seven days |
| 2027 | 17 May | 17 May | Same date this year |
| 2028 | 15 May | 15 May | Same date this year |
The 2027 and 2028 matches are not proof of equivalence. A reliable comparison includes 2026, where the first labeled week begins in the previous calendar year. Looking only at a future calendar with matching dates can hide the distinction.
These dates were independently checked by enumerating Mondays and computing Monday-start week 20, then comparing finite RFC recurrence expansion. No fiscal, school or workplace week numbering was inferred.
Inspect two matching-start yearly files
These are complete fictional calendar files for inspection and isolated practice. Identifiers and timestamps belong to the examples. No invitations or alarms are present. Keep your original export and use a separate test calendar before changing a live schedule; particular calendar-app import behavior has not been tested here.
Download practice twentieth monday of year (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VEVENT
UID:c95be13cfb1515e64d0ea869@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART;VALUE=DATE:20260518
SUMMARY:Twentieth Monday within year
RRULE:FREQ=YEARLY;COUNT=3;BYDAY=20MO
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDARDownload practice monday week twenty (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VEVENT
UID:d9aa1b2d17a1a42d1f1e69b2@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART;VALUE=DATE:20260511
SUMMARY:Monday numbered week 20
RRULE:FREQ=YEARLY;COUNT=3;BYWEEKNO=20;BYDAY=MO;WKST=MO
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAREach DTSTART matches its own rule. Both files have three occurrences, covering the listed 2026–2028 dates. Reusing May 18 as the start of the week 20 file would create an unsynchronized start rather than a valid test of equivalent schedules. [2]
Check the organization’s definition before importing
For a real reporting schedule, record the week start, the first-week definition and whether the label belongs to a calendar year, fiscal year or term. A calendar app’s displayed week number may have a separate preference; changing that visual setting does not by itself rewrite an exported recurrence.
If the requirement names an ordinal weekday, count those weekdays directly. If it names numbered weeks, use the specified week system and verify a year boundary. If the needed business definition is different from RFC BYWEEKNO, do not substitute the closest-looking rule without calculating the intended dates.
The first and twentieth selected dates, and a year with a boundary difference, make useful audit checkpoints. Keep the rule syntax and human label together so a future editor can recover the intended meaning.
Two complete year/week decisions
The two rules agree in 2027. Can I replace one with the other?
Only if the intended policy actually changes; agreement in one year is insufficient.
In 2026 the twentieth Monday is May 18, while Monday in week 20 is May 11. Their definitions differ even when particular years produce the same date.
Can BYDAY=20MO be combined with BYWEEKNO=20 to mean the same thing more clearly?
No. That numeric BYDAY combination is prohibited for YEARLY rules with BYWEEKNO.
Choose either the year-level weekday ordinal without BYMONTH/BYWEEKNO, or the week-number selector with nonnumeric BYDAY=MO. Then give the chosen rule a matching DTSTART.
Sources and further reading
- RFC 5545 §3.3.10Rule scope and exact example interpretation.
- RFC 5545 §3.8.5.3Rule scope and exact example interpretation.