RRULE Generator and Next Occurrence Tester

RRULE:FREQ=WEEKLY;BYDAY=MO,WE,FR;COUNT=12

What is an RRULE?

An iCalendar RRULE describes a repeating set of dates. It is used in ICS files and calendar APIs for meetings, reminders, subscriptions, and scheduled events. The rule works together with a start date; the RRULE alone does not contain the first occurrence's complete local time-zone context.

Common examples

Every weekday for 20 occurrences:

RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;COUNT=20

Every three months on the fifteenth day:

RRULE:FREQ=MONTHLY;INTERVAL=3;BYMONTHDAY=15

COUNT and UNTIL

COUNT limits the complete recurrence set, including the first matching occurrence. UNTIL stops expansion at a date or UTC timestamp. Do not use both in the same generated rule. An event without either value repeats indefinitely until another system-specific limit applies.

Dates that do not exist

A monthly rule for day 31 has no occurrence in a month without that date. It should not silently move to the last day of the month. Yearly events created on February 29 similarly skip non-leap years unless a more complex rule or application behavior says otherwise.

Preview scope and time zones

The tester implements the common FREQ, INTERVAL, COUNT, UNTIL, plain BYDAY, and BYMONTHDAY combinations created by this page. The complete iCalendar grammar also includes ordinal weekdays, BYSETPOS, week numbers, year days, explicit inclusions and exclusions, and calendar-scale extensions. Use a production recurrence library for rules outside the documented subset.

The input is interpreted in the browser's local time zone and each result also shows UTC. Daylight-saving transitions can change UTC offsets while local wall-clock time remains constant.

Recurrence syntax is defined by RFC 5545. Use the ICS Calendar File Generator to package an event, the Cron Expression Debugger for server schedules, or the World Clock to compare time zones. Rule data stays in your browser.