It runs every 15 minutes (at minutes 0, 15, 30 and 45) between 09:00 and 17:45, Monday to Friday. From 1 January 2026 at 00:00 UTC, the first run is that same day at 09:00.
Calculation assumptions
Checks a 5-field cron expression and shows its next runs in UTC and the value of each field. Supports lists, ranges, steps and names such as mon or jan.
minute hour day month weekday · * any · , list · - range · / step · 0 or 7 = Sunday
Checks a 5-field cron expression and shows its next runs in UTC and the value of each field. Supports lists, ranges, steps and names such as mon or jan.
All amounts use the same currency of your choice. These are estimates, not measurements or offers.
How to use this calculator
Before scheduling a crontab task, a backup or a server job, check that the expression does what you expect. Type the five fields (minute, hour, day of month, month and day of week) and a start date: you will see the next runs and how each field is read.
Worked example
*/15 in minutes: 0, 15, 30 and 45.
9-17 in hours and 1-5 in weekday: 9:00 to 17:59, Monday to Friday.
1 January 2026 is a Thursday, so the first run is that day at 09:00 UTC.
Example result
Minutes
0,15,30,45
Hours
9,10,11,12,13,14,15,16,17
Interpreting the result
Dates are shown in UTC, but cron uses the server time zone: if your server runs on local time, real runs happen at those local hours. If you restrict both day of month and day of week, cron runs when either one matches, not both: a common source of mistakes.
Frequently asked questions
How do I schedule something every day at 3 am?
With 0 3 * * *: minute 0, hour 3 and any day, month and weekday.
Does cron support seconds?
No. Classic Linux cron works in minutes; tools such as Quartz or systemd timers use different formats.
What do @reboot and @daily do?
They are shortcuts in some cron versions: @daily equals 0 0 * * * and @reboot runs at startup. This tool checks the five-field form.