⏱ Cron Expression Visualizer
See the next 10 runs of any cron schedule.
Last updated: November 8, 2026 · By the BoltQuickTools team
0-59
0-23
1-31
1-12
0-6 (Sun=0)
Next 10 Runs
Seeing the actual times a cron line will fire
When you are about to commit a crontab entry or a CI schedule, a list of real dates is a faster sanity check than reading the fields. This page gives you the next ten fire times with a countdown to each.
Using it
Type five space-separated fields into the Cron Expression box, or click a preset such as weekdays at 9 or every 15min, business hours. A one-line summary and the Next 10 Runs list update as you type. Countdowns are measured when the list is drawn and do not tick, so edit the box or reload for fresh ones.
Example output
Assume the page is open on Monday, November 2, 2026 at 08:00 in an en-US browser. For */15 9-17 * * 1-5 the summary reads:
Runs every 15 minutes of hour 9-17, on Mon through Fri.
and the list begins:
Mon, Nov 02, 2026 09:00 in 1h 0m
Mon, Nov 02, 2026 09:15 in 1h 15m
Mon, Nov 02, 2026 09:30 in 1h 30m
The last run each day is 17:45, because the range 9-17 includes the whole of hour 17.
Setting both day fields shows the classic trap. 0 0 1 * 1 is commonly read as "the 1st, if it is a Monday", but it means the 1st or any Monday:
Mon, Nov 09, 2026 00:00
Mon, Nov 16, 2026 00:00
Mon, Nov 23, 2026 00:00
Mon, Nov 30, 2026 00:00
Tue, Dec 01, 2026 00:00
Mon, Dec 07, 2026 00:00
Input that goes wrong quietly
This parser is lenient. Several mistakes produce no error, so compare the list against what you expected.
| You type | What happens |
|---|---|
0 9 * * 7 | Day of week runs 0 to 6 here, so 7 is discarded. The summary says "on undefined" and the list is empty. Use 0 for Sunday. |
0 9 * * 5-7 | Only Friday and Saturday are listed. |
0 25 * * * | Out-of-range values are dropped. The list is empty with no error. |
0 0 30 2 * | The date never exists. The list is empty with no message. |
5/15 * * * * | Read as just minute 5, so once an hour. Write 5-59/15 for every 15 minutes starting at 5. |
0 9 * * 1#2 | The #2 is ignored and every Monday is listed. 5L behaves the same way. |
1abc * * * * | Parsed as minute 1. |
Other forms do produce a Could not parse message: day and month names such as MON, macros such as @daily, a bare L, and any count other than five fields. When that happens the previous summary and list stay on screen below the error, so do not read them as the result for your new input.
Parser differences and time zones
How is this different from the cron parser?
The two overlap. This page is the better check for ordinary crontab lines: it treats the two day fields as either-match, which is what standard cron does, and it can look years ahead, so 0 0 29 2 * lists ten leap days. The cron parser adds a dropdown builder and understands L, W and #, but requires both day fields to match and only searches about one year.
Are the times UTC?
No, they use your browser's time zone. Most servers run cron in their own zone, often UTC. The timezone converter helps you line the two up.
Are seconds supported?
No. Six-field schedules from Quartz or Spring fail with "expression must have exactly 5 fields".
Can I get the times as timestamps?
The list is display text only, with no export. Convert individual dates with the timestamp converter.