Cron every 15 minutes
*/15 fires at :00, :15, :30 and :45 of every hour. Writing 0,15,30,45 in the minute field is exactly equivalent and some people find it clearer — cron treats a step and an explicit list identically once expanded.
Every 15 minutes.
Next runs — UTC
- Sun, 25 Oct 2026, 00:45
- Sun, 25 Oct 2026, 01:00
- Sun, 25 Oct 2026, 01:15
- Sun, 25 Oct 2026, 01:30
- Sun, 25 Oct 2026, 01:45
Five fields. Runs in the server's local timezone.
Cron uses the server’s timezone, which is often not yours. Check before you trust a time.
Fields
- minute0–59
- hour0–23
- dom1–31
- month1–12
- dow0–7
The expression
*/15 * * * *
Edit it above to see the next run times update, or switch dialect if your scheduler uses a different format.
Frequently asked questions
- Is */15 the same as 0,15,30,45?
- Yes, identical. The step form expands to that list. Use whichever you find easier to read six months from now.
- How do I offset a job so it doesn't run at the same time as everything else?
- Start the step somewhere other than zero: 7-59/15 fires at :07, :22, :37 and :52. Staggering jobs like this is the simplest way to stop every cron on the box waking at once.
- Does */15 drift over time?
- No. Cron matches wall-clock time rather than counting from the last run, so the schedule stays anchored to the hour no matter how long a run takes.