Skip to content

Cron Expression Parser - Next Run Times Explained

*/15

Minute

0-59

*

Hour

0-23

*

Day (month)

1-31, L, W

*

Month

1-12

*

Day (week)

0-6, L, #

Description

At minutes 0, 15, 30, 45 past hour every hour.

Next 10 Executions

  1. 1Tue, 10 Nov 2026, 10:45
  2. 2Tue, 10 Nov 2026, 11:00
  3. 3Tue, 10 Nov 2026, 11:15
  4. 4Tue, 10 Nov 2026, 11:30
  5. 5Tue, 10 Nov 2026, 11:45
  6. 6Tue, 10 Nov 2026, 12:00
  7. 7Tue, 10 Nov 2026, 12:15
  8. 8Tue, 10 Nov 2026, 12:30
  9. 9Tue, 10 Nov 2026, 12:45
  10. 10Tue, 10 Nov 2026, 13:00

Read a cron expression in plain English

Paste an expression from a crontab, a CI config or a scheduler and the parser shows what each field means, a plain English description, and the next 10 run times. Seeing actual dates is the quickest way to catch a schedule that is off by a day or runs far more often than you meant. The presets fill in common schedules to start from.

Example

30 6 * * 1-5 is described as "At 06:30, on Monday, Tuesday, Wednesday, Thursday, Friday". 0 */6 * * * runs at 00:00, 06:00, 12:00 and 18:00. 0 0 29 2 * only runs in leap years, so it lists just two runs (29 February 2028 and 2032), because the parser searches eight years ahead.

Syntax reference

  • * matches every value in the field.
  • 5 matches a specific value.
  • 1-5 matches a range of values (inclusive).
  • 1,3,5 matches a list of specific values.
  • */15 matches every 15th value starting from the minimum.
  • 1-10/2 matches every 2nd value in the range 1 to 10.
  • ? means "no specific value" in a day field. It works like *.
  • mon-fri, jan,jul: three-letter names work in the month and day-of-week fields, in any case.

Macros and seconds

The shortcuts @yearly (or @annually), @monthly, @weekly, @daily (or @midnight) and @hourly are expanded to their 5-field form. @reboot runs once when the cron daemon starts, so it has no next run times. If you enter 6 fields, the first is seconds (0-59), as used by Spring, Quartz and node-cron. Quartz's optional seventh year field is not supported.

Quartz day syntax

  • L in day of month is the last day of the month. L-3 is three days before it.
  • LW is the last weekday (Monday to Friday) of the month.
  • 15W is the weekday nearest the 15th. It never crosses into another month, so 1W on a Saturday runs on Monday the 3rd.
  • 5L in day of week is the last Friday of the month.
  • 1#2 in day of week is the second Monday of the month.

Day-of-week numbers here follow Unix cron (0 or 7 is Sunday, 1 is Monday). Quartz itself counts 1 as Sunday, so use day names such as MON#2 if you are writing for Quartz. Values outside a field's range, such as minute 60, are reported as errors rather than ignored.

Related Tools

Frequently Asked Questions

What are the five cron fields?
In order: minute (0-59), hour (0-23), day of month (1-31), month (1-12 or jan-dec) and day of week (0-7 or sun-sat, where both 0 and 7 are Sunday). 30 2 * * 1 means 02:30 every Monday. Each field takes a single value, a range (1-5), a list (1,15), a wildcard (*) or a step (*/15).
What does */15 mean?
Every 15th value, counted from the start of the field's range. In the minute field that is 0, 15, 30 and 45. Steps restart each hour, so */25 runs at 0, 25 and 50, then 0 again only 10 minutes later. A range can have a step too: 1-10/2 is 1, 3, 5, 7, 9.
Why does 0 9 13 * 5 run on more than Friday the 13th?
When both day of month and day of week are set, standard cron runs on days that match either one, not both. 0 9 13 * 5 runs at 09:00 on the 13th of every month and on every Friday. This parser follows the same rule, so the next run times show it. If you need both conditions, schedule one of them and check the other inside the script.
Which time zone are the next run times in?
Your browser's local time zone. Cron itself uses the time zone of the machine or service running it, and many (GitHub Actions, most cloud schedulers by default, Docker containers) use UTC. If your server is in UTC and you are not, shift the hour field accordingly.
What about 6-field cron with seconds?
If you enter six fields, the first is read as seconds (0-59), as in Spring, Quartz and node-cron. Standard Unix crontab and GitHub Actions only accept five fields, so a 6-field expression pasted there will be rejected or misread.