FiggyrA little everyday clarity.

Tech & Network / Everyday tools

Cron expression builder

Choose a common schedule or edit a five-field expression. Preview actual UTC instants alongside the selected local time.

Build your schedule.

Next five matches.

Five numeric fields. Zone is configured separately in your scheduler. Preview uses wall-clock matching, not daemon catch-up rules.

The working, clearly explained

Behind the numbers.

FIGGYR / FIELD NOTES

How it works

Supported subset: numeric five-field Unix-style cron, with *, ascending ranges, comma lists and steps after * or a range. No names, command, seconds, year, macros or Quartz extensions. When both day-of-month and day-of-week contain no *, either may match; if either contains *, both conditions must match. Preview scans UTC minutes strictly after the selected start, for up to 366 days and five matches. It uses this browser’s time-zone database.

The formulaminute hour day-of-month month day-of-week
Minute 0–59 · hour 0–23 · day 1–31 · month 1–12 · weekday 0–7 (0 and 7 = Sunday)

Put it into practice

EXAMPLE

0 9 * * 1-5 matches 09:00 Monday through Friday in the selected zone.

EXAMPLE

*/15 * * * * runs on minutes 0, 15, 30 and 45 of every hour; it is not a rolling 15-minute delay.

Good to know

What happens at daylight-saving changes?

This preview uses wall-clock matching. A local time that does not exist is skipped. A repeated local time can appear twice with different UTC offsets. Actual cron daemons may implement different catch-up rules; confirm your scheduler’s behavior.

Does the time zone become part of the expression?

No. A five-field expression contains no time zone. Configure the same zone separately in your scheduler. This tool does not create or run jobs.

Why are fewer than five runs shown?

Sparse or impossible dates may have fewer than five matches in the bounded 366-day search. The result says when the search limit is reached. It does not claim no future match exists.