1. The recurrence
A bare FREQ=... works too: then give the start below. A pasted event or whole .ics file is fine; the first event's recurrence is read.
2. What the rule says
Dates
| # | Local date and time | Day | UTC | Note |
|---|
Common rules, written correctly
- Last day of every month:
FREQ=MONTHLY;BYMONTHDAY=-1 - The 30th, or the last day when the month is shorter:
FREQ=MONTHLY;BYMONTHDAY=28,29,30;BYSETPOS=-1 - Last weekday (Monday to Friday) of the month:
FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1 - Second Tuesday of every month:
FREQ=MONTHLY;BYDAY=2TU - Every other week on Tuesday and Thursday:
FREQ=WEEKLY;INTERVAL=2;BYDAY=TU,TH;WKST=MO(write WKST; it decides which weeks pair up) - US Thanksgiving:
FREQ=YEARLY;BYMONTH=11;BYDAY=4TH
Checking a whole .ics file for import errors (missing UID, bad line folding, wrong value types)? Use the ICS calendar checker. Guide: why a recurring event skips months, or shows up twice. Scheduling a cron job across a clock change instead? The cron DST drift check shows which runs a DST change skips or doubles.
Questions
Why does my monthly recurring event skip some months?
Because RFC 5545 drops dates that do not exist rather than moving them. A rule that repeats monthly from the 31st (FREQ=MONTHLY with DTSTART on the 31st, or BYMONTHDAY=31) fires only in the seven months that have a 31st. For the last day of every month write BYMONTHDAY=-1; for the 30th, or the last day of a shorter month, write BYMONTHDAY=28,29,30;BYSETPOS=-1. The tool prints the fixed rule for your case.
Why does my calendar show an extra occurrence on the start date?
RFC 5545 makes DTSTART the first occurrence even when the rule would not produce that date, and it counts toward COUNT. FREQ=WEEKLY;BYDAY=TU with a DTSTART on a Monday happens on that Monday too. Libraries such as python-dateutil leave the Monday out, so apps disagree. Move DTSTART to the first date the rule makes.
What happens to a recurring event at a time the clocks skip?
RFC 5545 reads a local time that a forward clock change skips with the UTC offset in force before the change, so a daily 02:30 event in New York happens at 03:30 on the day clocks spring forward. A time that happens twice when clocks go back means the first of the two. The tool marks each such date and gives its UTC time.
What does WKST do in an RRULE?
WKST names the day weeks start on (Monday by default). It only matters for a WEEKLY rule with an INTERVAL above 1 and several BYDAY days, and for BYWEEKNO. FREQ=WEEKLY;INTERVAL=2;BYDAY=TU,SU from Tuesday 1997-08-05 gives the 5th, 10th, 19th and 24th with WKST=MO but the 5th, 17th, 19th and 31st with WKST=SU. The tool warns when your rule depends on it.
How do I write every last weekday of the month as an RRULE?
FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1. BYDAY collects every weekday in the month and BYSETPOS=-1 keeps the last one. BYSETPOS=1 gives the first weekday.
Is anything I paste uploaded?
No. The rule is expanded in this browser tab. There are no accounts, cookies or analytics vendors, and the command-line version makes no network calls.
From the command line, or an agent
The same engine with no dependencies and no network: node cli.mjs 'FREQ=MONTHLY;BYDAY=-1FR' --start 2026-01-30T17:00 --tz Europe/London prints the dates and findings, --json for scripts, --strict to fail a CI job on warnings. Pipe an event in with -. Source and README.