Cron every 5 minutes

The cron expression for every 5 minutes is:

*/5 * * * *

Runs every 5 minutes: :00, :05, :10 and so on to :55.

288 times a day

Standard 5-field cron

Monitor this schedule Open in translator Change it in the generator

Next 10 runs

For */5 * * * *, in the timezone you pick. Cron uses the server's timezone.

Times in UTC as of the last site update. They refresh when the page loads in a browser.

Timezone

#	Date and time	When
1	Oct 29, 2026, 22:15	Thursday
2	Oct 29, 2026, 22:20	Thursday
3	Oct 29, 2026, 22:25	Thursday
4	Oct 29, 2026, 22:30	Thursday
5	Oct 29, 2026, 22:35	Thursday
6	Oct 29, 2026, 22:40	Thursday
7	Oct 29, 2026, 22:45	Thursday
8	Oct 29, 2026, 22:50	Thursday
9	Oct 29, 2026, 22:55	Thursday
10	Oct 29, 2026, 23:00	Thursday

How to read /5 * * *

*/5 in the minute field takes every fifth minute, starting at 0. The other four * fields mean every hour, every day of the month, every month and every day of the week.

Field	Value	Meaning	Allowed
Minute	*/5	Every 5 minutes, from minute 0	0-59
Hour	*	Every hour	0-23
Day of month	*	Every day of the month	1-31
Month	*	Every month	1-12 or jan-dec
Weekday	*	Every day of week	0-7 or sun-sat

Watch out for

Runs are aligned to the clock, not to when you saved the crontab: a job added at 10:03 first runs at 10:05, not 10:08.
Many jobs fire at :00, :05, :10. To move yours off those minutes, shift the start: 2-59/5 * * * * runs at :02, :07, :12 and so on.
On GitHub Actions this is the shortest schedule allowed, and runs can start late when GitHub is busy.

Often used for: Cache refreshes, data syncs, report exports and health checks. One of the most common cron schedules.

Use it in

crontab

*/5 * * * * /path/to/your-script.sh

Edit with crontab -e. Runs in the server's timezone.

Kubernetes CronJob

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

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

GitHub Actions

on:
  schedule:
    - cron: '*/5 * * * *'
      timezone: "Etc/UTC"
jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: ./your-script.sh

Without timezone, GitHub runs schedules in UTC. It runs them at most every 5 minutes, and a run can start late when GitHub is busy.

All cron schedules

Cron does not tell you when a job stops

Know when a job on this schedule does not run.

Your job pings Drumbeats when it finishes. If a ping does not arrive on schedule, you get an alert. No SDK, free for up to 50 monitors.

Monitor this schedule Set up with AI agent

Free for up to 50 monitors · Setup in 60 seconds · No credit card required