Paste a cron line, pick a time zone, see what it means and when it runs next (daylight-saving aware).
At 02:30, on Sunday.
2026-10-11T02:30:00-04:002026-10-18T02:30:00-04:002026-10-25T02:30:00-04:002026-11-01T02:30:00-05:002026-11-08T02:30:00-05:002026-11-15T02:30:00-05:002026-11-22T02:30:00-05:002026-11-29T02:30:00-05:002026-12-06T02:30:00-05:002026-12-13T02:30:00-05:00Add the next runs to a calendar (.ics)
curl 'https://cron.wickkit.cc/?e=*/15+9-17+*+*+1-5&tz=Europe/Berlin&n=5' curl 'https://cron.wickkit.cc/api?e=@weekly&tz=America/New_York' # JSON curl 'https://cron.wickkit.cc/ics?e=0+3+*+*+*&tz=Europe/Berlin&name=Backups' # calendar
The calendar has the next 50 runs (n, up to 100), each d minutes long (default 15), titled name.
Subscribe to the /ics URL ("From URL" in Google Calendar, "New Calendar Subscription" in Apple Calendar) and it keeps rolling forward.
Five fields (minute hour day-of-month month day-of-week), names like mon and jan, and the @daily-style macros.
When both day fields are set, a day matches if either matches, as in standard cron.
A time skipped by a daylight-saving jump doesn't run; a time that happens twice runs once.