Every 15 minutes during business hours Cron Expression (*/15 9-17 * * 1-5)

*/15 9-17 * * 1-5 Open in Cron Expression Parser

Field by field

Field	Value	Matches
Minute	*/15	0, 15, 30, 45
Hour	9-17	9, 10, 11, 12, …, 17
Day of month	*	Every value
Month	*	Every value
Day of week	1-5	Monday Tuesday Wednesday Thursday Friday

Next run times

Example: the first 6 runs after January 1, 2026 (UTC).

Thu, Jan 1, 2026, 09:00
Thu, Jan 1, 2026, 09:15
Thu, Jan 1, 2026, 09:30
Thu, Jan 1, 2026, 09:45
Thu, Jan 1, 2026, 10:00
Thu, Jan 1, 2026, 10:15

Ready-to-use versions

crontab

*/15 9-17 * * 1-5 /path/to/command

Add the line with crontab -e. It runs in the server's time zone unless CRON_TZ or TZ is set.

Kubernetes CronJob

apiVersion: batch/v1
kind: CronJob
metadata:
  name: every-15-minutes-during-business-hours
spec:
  schedule: "*/15 9-17 * * 1-5"
  timeZone: "Etc/UTC"
  concurrencyPolicy: Forbid
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: OnFailure
          containers:
            - name: job
              image: busybox:1.36
              command: ["/bin/sh", "-c", "date; echo run"]

Set spec.timeZone (Kubernetes 1.27+); without it the schedule follows the controller manager's time zone, usually UTC.

GitHub Actions

on:
  schedule:
    - cron: '*/15 9-17 * * 1-5'
  workflow_dispatch:

GitHub Actions always uses UTC, accepts intervals of 5 minutes or more, and may start scheduled runs late under load.

Quartz

0 */15 9-17 ? * MON-FRI

Quartz puts seconds first and needs ? in either day-of-month or day-of-week. Days are 1–7 from Sunday, so names are safer.

Spring

@Scheduled(cron = "0 */15 9-17 * * MON-FRI")

Spring @Scheduled(cron = …) takes six fields: seconds, then the usual five.

FAQ

› How do I stop exactly at 17:00?

Cron cannot end mid-hour with one line. Use */15 9-16 * * 1-5 plus a second line 0 17 * * 1-5.

› Which time zone does */15 9-17 * * 1-5 run in?

Cron uses the time zone of the machine or service that runs it. On Linux that is the system time zone unless CRON_TZ or TZ is set; Kubernetes CronJobs accept spec.timeZone; GitHub Actions always uses UTC.

› How can I check this schedule before deploying it?

Open */15 9-17 * * 1-5 in the Cron Expression Parser on this site. It explains each field and lists the upcoming runs in your local time or UTC, right in your browser.