Practical guide

BYDAY and BYMONTHDAY: Why Friday the 13th Uses Both Filters

When BYDAY and BYMONTHDAY both limit a monthly recurrence, a date must satisfy both filters. A Friday-the-13th rule selects only dates that are Friday and the 13th, with long gaps possible between occurrences. It does not combine every Friday with every monthly 13th.

Readers inspecting recurrence exports and constructing a finite calendar schedule. · 7 minute read · Published

Write the intended AND or OR in plain language

“Friday and the 13th” requires both conditions on the same date. “Every Friday, plus the 13th each month” describes a union of two schedules. They are different reader decisions; a comma inside one field does not turn two separate filters into an OR operation.

With FREQ=MONTHLY;BYDAY=FR;BYMONTHDAY=13, BYMONTHDAY limits the dates to day 13, and BYDAY further limits them to Friday. RFC 5545’s rule processing order and expand/limit behavior make the intersection explicit. [1]

This example explains date selection only. It makes no prediction about luck, risk or actual events associated with Friday the 13th. Use it as a concrete counterexample when an exported rule seems to have fewer dates than expected.

Check one date that fails each condition

On a narrow screen, swipe within this table to read the remaining columns.

Original January 2027 filter checks
DateIs the 13th?Is Friday?Selected by both filters?
13 January, WednesdayYesNoNo
15 January, FridayNoYesNo
No Friday the 13th in JanuaryNot applicableNot applicableNo January occurrence

Neither January 13 nor January 15 survives both filters. January is skipped rather than repaired by shifting the date to the nearest Friday. A valid date that fails a weekday filter is different from an invalid date such as February 31, but both can produce no occurrence in a particular month.

Both filters must match; complete values are in the adjacent worked table.
Both filters must match. Original explanatory diagram; use the complete table for every dated result.

Enumerate four valid occurrences from a matching start

On a narrow screen, swipe within this table to read the remaining columns.

Original finite Friday the 13th recurrence
OccurrenceSelected startGap after prior occurrence
113 November 2026Matching DTSTART
213 August 2027Nine calendar months
313 October 2028Fourteen calendar months
413 April 2029Six calendar months

All four selected dates are Fridays. COUNT=4 therefore covers November 2026 through April 2029, not four consecutive months. Months that do not have a Friday on their 13th contribute no candidate.

Start on the matching November 13 date. Do not imitate an example with an unrelated DTSTART and assume the application repairs it. RFC 5545 says the recurrence set is undefined when the start is not synchronized with the recurrence rule. [2]

Inspect a complete finite all-day specimen

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 friday thirteenth intersection (.ics)

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Recurrence Practice 1.0//EN
BEGIN:VEVENT
UID:12304c85e99f9b360affe334@daymooncalendar.com
DTSTAMP:20261109T000000Z
DTSTART;VALUE=DATE:20261113
SUMMARY:Friday the 13th practice
RRULE:FREQ=MONTHLY;COUNT=4;BYDAY=FR;BYMONTHDAY=13
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR

The DATE start does not mean midnight in a particular zone. Its displayed date should be checked as an all-day entry. This file carries a finite count, so it does not request an unbounded schedule. Compare all four expected dates in a separate test calendar.

Represent a union deliberately when that is the requirement

For every Friday plus every monthly 13th, do not add a second RRULE to the same VEVENT as a shortcut. RFC 5545 says the recurrence set generated by multiple RRULE properties is undefined. [2]

Use separate events for genuinely separate schedules, with distinct UIDs, or calculate a finite union and record the explicit confirmed dates. Decide what should happen when the two schedules coincide: two distinct activities might both matter, while one shared reminder should appear only once.

For one reminder represented by RDATE additions, deduplicate its inclusion set and apply any EXDATE values afterwards. The date-set audit guide explains that operation. Establishing a clear union policy avoids deleting an intentional separate activity just because it shares a date.

Two complete filter decisions

Wednesday January 13 appears in the rule’s month-day list. Why is there no event?

It fails the Friday filter.

Day 13 alone is insufficient when BYDAY=FR is also present. January 15 is Friday but fails the day 13 filter, so neither date is selected.

COUNT=4 ends in April 2029. Is the monthly frequency being ignored?

No. Each month is evaluated, but only matching dates count.

Starting November 13 2026, the next matching dates are August 13 2027, October 13 2028 and April 13 2029. Nonmatching months do not supply replacement starts.

Sources and further reading

  1. RFC 5545 §3.3.10Rule scope and exact example interpretation.
  2. RFC 5545 §3.8.5.3Rule scope and exact example interpretation.