Technical and media time

RRULE Recurrence Generator and Tester

Create a basic iCalendar recurrence rule and preview its occurrences.

PrivacyRuns in your browser
OutputTechnical console
CostFree to use
Technical console

Enter your details

Adjust the planning assumptions below.

Calculations stay in this browser. Saved inputs and recent results use local browser storage until you clear them.

Your schedule will appear here

Results update after calculation and include a visual timeline, calendar, or dashboard.

Purpose and scope

What this technical calculator produces

Create a basic iCalendar recurrence rule and preview its occurrences.

The RRULE Recurrence Generator and Tester derives a readable value from First occurrence, Frequency, Interval, Occurrences, and Weekly day; Maintain Weekly day beside the copied output.

InterfaceTechnical console
OutputReadable and copyable values

Instructions

How to use this calculator

Enter the first occurrence, frequency, interval, count, and weekly day when relevant.

  1. Choose First occurrence and Frequency exactly as supplied by the recorded basis.
  2. Derive the RRULE Recurrence Generator and Tester conversion and test Weekly day with the copyable output.
  3. Recheck Weekly day against its source because it controls part of the RRULE Recurrence Generator and Tester interpretation.
  4. Test the RRULE Recurrence Generator and Tester reference with the Weekly day definition or convention.

Calculation

Method used

The generator produces a basic recurrence rule and advances occurrences by calendar day, week, month, or year.

Occurrence n advances DTSTART by n × INTERVAL in the selected calendar frequency.

The RRULE Recurrence Generator and Tester relates First occurrence, Frequency, and Interval to the converted value; maintain the Weekly day precision or unit convention.

Calculation method last reviewed: June 21, 2026.

Verification

References

Reference and calculation method reviewed: June 21, 2026.

Worked scenario

Example calculation

Example: A weekly rule with interval two and count eight produces eight occurrences every other week from the selected start.

Test the RRULE Recurrence Generator and Tester worked value with Weekly day, then scan its precision and format.

Interpretation

Validating the generated output

Use the rule text for interchange and the occurrence preview to detect an incorrect anchor or interval.

Scan the RRULE Recurrence Generator and Tester output against Weekly day before sending its unit, epoch, or syntax elsewhere.

Boundaries

Important edge cases and limitations

Complex BYSETPOS rules, exclusions, end dates, multiple weekdays, invalid month days, and named time zones are not fully implemented.

Modify the RRULE Recurrence Generator and Tester convention when Weekly day uses another epoch, precision, or syntax rule.

Input audit

Checklist for this calculation

  • Scan the RRULE Recurrence Generator and Tester unit or epoch in First occurrence and Frequency.
  • Test Weekly day with the RRULE Recurrence Generator and Tester copyable output.
  • Maintain Interval, Occurrences, and Weekly day beside the RRULE Recurrence Generator and Tester; include Weekly day in any saved or shared record.
  • Test the RRULE Recurrence Generator and Tester reference with the Weekly day date and use case.

Practical use

Recommended workflow

Test the generated rule in the destination calendar system and include the intended time-zone identifier.

Questions

Frequently asked questions

What is DTSTART's role?

DTSTART anchors the recurrence. Changing it can change both the first event and how interval-based occurrences line up.

When should RFC 5545: Internet Calendaring and Scheduling be checked for the

Test RFC 5545: Internet Calendaring and Scheduling with Weekly day whenever the RRULE Recurrence Generator and Tester threshold affects a decision. Maintain its version or access date beside First occurrence.

How often should a saved rrule recurrence generator and tester result be reconsidered?

Refresh the RRULE Recurrence Generator and Tester whenever the schedule source changes First occurrence, Weekly day, or their relationship. Label earlier runs as historical assumptions.

What makes First occurrence important to the

First occurrence identifies the RRULE Recurrence Generator and Tester source value, while Weekly day specifies part of its output convention. Confirm both before copying the converted value.

When would a different Weekly day require a fresh rrule recurrence generator and tester result?

Run the RRULE Recurrence Generator and Tester twice with the same First occurrence and a different Weekly day. Compare both RRULE Recurrence Generator and Tester output forms before adopting the new Weekly day convention.