A quarter-hour cadence balances freshness against load nicely, which is why it is common for cache warming, log rotation, and scheduled syncs. The plain-English summary and live next runs appear below.

*/15 * * * *

Every 15 minutes.

Next 5 runs (local time)
6/24/2026, 7:15:00 AM
6/24/2026, 7:30:00 AM
6/24/2026, 7:45:00 AM
6/24/2026, 8:00:00 AM
6/24/2026, 8:15:00 AM
Field breakdown of */15 * * * *
FieldValueMeaning
Minute*/150, 15, 30, 45
Hour*every hour
Day of month*every day
Month*every month
Day of week*every weekday
Worked example
*/15 * * * *Runs at :00, :15, :30 and :45 — four times an hour.

Equivalent to writing 0,15,30,45 * * * * explicitly.

Frequently asked questions

What times does */15 * * * * trigger?

At minute 0, 15, 30, and 45 of every hour. That is four runs an hour, or 96 per day.

Is */15 the same as 0,15,30,45?

Yes. The step form */15 expands to the explicit list 0,15,30,45, so both expressions produce identical schedules.

When should I use a 15-minute schedule?

It suits tasks that should feel fairly fresh but do not need minute-level immediacy, such as cache refreshes, metrics aggregation, or pulling updates from an external service.

Related conversions

Need more options? Try the full Cron Expression Parser.