AZ Tools

Cron Next Runs

Time

Parses standard 5-field cron (`minute hour day month weekday`) with ranges (`1-5`), lists (`1,3,5`), steps (`*/15`), and month / weekday aliases (`mon`, `jan`). The result list shows the next runs starting from now (or a fixed timestamp), in your local timezone. When both day-of-month and day-of-week are restricted, either match counts as a hit — matching the original Vixie cron semantics.

Upcoming runs
  • #16/3/2026, 9:00:00 AM
  • #26/4/2026, 9:00:00 AM
  • #36/5/2026, 9:00:00 AM
  • #46/8/2026, 9:00:00 AM
  • #56/9/2026, 9:00:00 AM
  • #66/10/2026, 9:00:00 AM
  • #76/11/2026, 9:00:00 AM
  • #86/12/2026, 9:00:00 AM

Times are in your local timezone — same one your browser is set to.

How to use

  1. Type a cron expression. The default `0 9 * * 1-5` means 9 AM on weekdays.
  2. Optionally set a different start time — useful for back-calculating from a past anchor or projecting from a future date.
  3. Pick how many upcoming runs to list (up to 50).

Frequently asked questions

Is `1 * * * *` once a day or once an hour?
Once an hour, at minute 1 of every hour. The first field is the minute — a literal value means "only when the clock reaches this value", and the other fields default to `*` (any). To run once a day at 1 AM, you'd write `0 1 * * *`.
What's the deal with day-of-month vs weekday?
When both fields are something other than `*`, cron treats them as OR: the job runs if either condition matches. `0 0 1 * 1` fires on the 1st of every month and on every Monday. If you want AND, you have to enforce it inside the job itself.
Does this support 6-field (with seconds) or quartz cron?
Not yet — this is plain Unix cron, 5 fields starting from the minute. Quartz introduces a seconds field and additional features like `L`, `W`, and `#`.

Related tools