Is `* * * * *` every minute?

Yes. All wildcards, so every minute.

Does `0 0 1 * MON` work?

No. This tool takes numbers only (0-6 Sun-Sat, or 1-7 Mon-Sun; 7 is the same as 0).

The tool uses the server's time-zone database and date arithmetic. DST behavior varies by scheduler; this preview does not guarantee every system's missed-run or repeated-run policy. Verify boundary dates in the target scheduler.

Why does 0 9 1 * 1 not require the first day to be Monday?

When both day fields are restricted, standard cron uses OR: it matches the first of each month and every Monday. Add a condition in the job for AND behavior.

Will calculating the schedule run the task?

No. This only parses the expression and lists future matches. It does not connect to your server or add a crontab entry. Configure the task on the target system separately.

Cron parser

Compute the next N runs of a standard 5-field cron expression

Computed on this site’s server

Enter five cron fields, choose a time zone and result count, then calculate. This previews times; it does not create, run or host scheduled jobs.

Enter a cron expression to compute the next runs.

Example

Input

*/15 9-17 * * 1-5

Example result

09:00, 09:15, 09:30, 09:45, …, 17:45

Every 15 minutes during hours 9 through 17, Monday to Friday, in the selected zone. The range includes 17:45.

Technical details & limits

Fields are minute, hour, day of month, month and weekday; seconds and years are absent. Both 0 and 7 mean Sunday. Restricted day-of-month and weekday fields use OR matching. Only numbers and * / , - are supported, not Quartz ? L W # or month names. Search starts after the current minute, covers up to eight years and returns at most 20 runs.

About this tool

Parse five-field cron expressions and list upcoming runs in a selected time zone, with ISO 8601 and Unix-second output. Supports wildcards, steps, lists and ranges for checking recurring schedules.

Use cases

Sanity-check a crontab you just wrote — when will it actually fire?
Debug a job that has not run all day — often day-of-month and weekday are both restricted with the wrong semantics.
Move a cron to a new time zone and confirm the trigger times still fit the intent.

How to use

Enter a five-field Cron expression, such as */15 9-17 * * 1-5.
Pick the time zone the schedule should be evaluated in.
Pick how many upcoming runs to list (up to 20).

Input & output

Input: A standard 5-field cron string. No L / W / # / weekday names.
Output: The next N fire times in the chosen zone as local time, ISO 8601 and Unix timestamp.
Limits: Search window is fixed at 8 years — beyond that, an unmatched expression returns “no runs in the next 8 years”.

Notes

When both day-of-month and weekday are restricted, Vixie cron uses OR (either match fires). This differs from Quartz — worth knowing.

FAQ

Is `* * * * *` every minute?: Yes. All wildcards, so every minute.
Does `0 0 1 * MON` work?: No. This tool takes numbers only (0-6 Sun-Sat, or 1-7 Mon-Sun; 7 is the same as 0).
What about DST?: The tool uses the server's time-zone database and date arithmetic. DST behavior varies by scheduler; this preview does not guarantee every system's missed-run or repeated-run policy. Verify boundary dates in the target scheduler.
Why does 0 9 1 * 1 not require the first day to be Monday?: When both day fields are restricted, standard cron uses OR: it matches the first of each month and every Monday. Add a condition in the job for AND behavior.
Will calculating the schedule run the task?: No. This only parses the expression and lists future matches. It does not connect to your server or add a crontab entry. Configure the task on the target system separately.

Related tools

Cron parser · Compute the next N runs of a standard 5-field cron expression — Cron parser — Tool illustration · dayeku.com