Cron every 20 minutes

*/20 * * * *

Runs three times an hour, at :00, :20 and :40.

What each field means

FieldPositionMeaning
*/20minuteevery 20th minute (0, 20, 40)
*hourevery hour
*day of monthevery day of month
*monthevery month
*day of weekevery day of week

Example run times

Starting from Wednesday 07 Jan 2026, 10:17, the next runs are:

  • Wed 07 Jan 2026, 10:20
  • Wed 07 Jan 2026, 10:40
  • Wed 07 Jan 2026, 11:00
  • Wed 07 Jan 2026, 11:20
  • Wed 07 Jan 2026, 11:40
  • Wed 07 Jan 2026, 12:00

How often it runs

  • 72 runs on each day it is active.
  • Active on 365 of the 365 days in 2026, for 26,280 runs that year.
  • Runs are always exactly 20 minutes apart.

Use it on your platform

Linux crontab

*/20 * * * * /path/to/command

Edit with crontab -e. Cron uses the server's local time zone.

GitHub Actions

on:
  schedule:
    - cron: '*/20 * * * *'

Schedules are evaluated in UTC, and runs can start late when GitHub is busy.

Kubernetes CronJob

apiVersion: batch/v1
kind: CronJob
metadata:
  name: my-job
spec:
  schedule: "*/20 * * * *"
  timeZone: "Etc/UTC"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
            - name: my-job
              image: busybox
              command: ["sh", "-c", "date"]
          restartPolicy: OnFailure

Without timeZone, the schedule follows the time zone of the kube-controller-manager.

AWS EventBridge

cron(0/20 * * * ? *)

AWS uses six fields (the last is the year), needs ? in either day-of-month or day-of-week, and counts weekdays from 1 = Sunday, so names like MON are safer than numbers. EventBridge rules run in UTC; EventBridge Scheduler lets you choose a time zone.

Spring @Scheduled

@Scheduled(cron = "0 */20 * * * *")

Spring adds a seconds field at the start, so prepend 0 to run at second zero.

Quartz

0 0/20 * * * ?

Quartz also starts with seconds and, like AWS, requires ? in one of the day fields.

Related schedules