Cron Every 5 Minutes from :02: 2-59/5 * * * *

Every 5 minutes, starting at minute 02. On the days it matches that means 288 runs per day, or roughly 105,120 a year. Below are the field-by-field reading, the exact minutes it lands on, and ready-to-paste blocks for crontab, Kubernetes and GitHub Actions.

The five fields, one at a time

Cron reads left to right, from the finest unit to the coarsest. This expression fills them like so:

The exact minutes it fires

Because the minute field resolves to 12 specific values, each hour has 12 trigger points: :02, :07, :12, :17, :22, :27, :32, :37, :42, :47, :52, :57.

Everything in this schedule is anchored to the top of the hour. If the box also runs other jobs at :00, shift this one with a range like 2-59/5 instead of */5 — same cadence, no thundering herd.

Paste it in

2-59/5 * * * *  /usr/bin/env bash /opt/jobs/every-5-minutes-offset.sh >> /var/log/every-5-minutes-offset.log 2>&1

apiVersion: batch/v1
kind: CronJob
metadata:
  name: every-5-minutes-offset
spec:
  schedule: "2-59/5 * * * *"
  concurrencyPolicy: Forbid
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: Never
          containers:
            - name: every-5-minutes-offset
              image: alpine:3.20
              command: ["/bin/sh", "-c", "echo running every-5-minutes-offset"]

on:
  schedule:
    - cron: '2-59/5 * * * *'
jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - run: echo "running every-5-minutes-offset"

Before you ship it

• Absolute paths only. Cron does not read your shell profile, so relative commands and $PATH lookups fail silently.
• Stars mean "every value", not "ignore the field". A * still participates in matching; it just matches everything.
• Overlap protection. A run that takes longer than the gap will stack. Add flock -n for shell jobs, or concurrencyPolicy: Forbid in Kubernetes.
• Log something. Cron mails output to a mailbox nobody reads; redirect to a file and rotate it.

Frequently asked

What is the cron expression for every 5 minutes from :02?
It is 2-59/5 * * * *. The engine reads it as: Every 5 minutes, starting at minute 02. On a day the schedule matches, it fires 288 times, and across a calendar year it fires about 105,120 times.

How many times a day does every 5 minutes from :02 run?
On the days it is allowed to run, 288 times: 12 trigger points per hour across 24 hours of the day. Because the schedule matches 365 days in a non-leap year, the yearly total is 105,120.

Why does the job still fail with 2-59/5 * * * * in crontab?
Almost always the environment, not the schedule. Cron runs with a near-empty PATH and no shell profile, so node, python3 or docker resolve to nothing. Use absolute paths, and redirect both streams (>> /var/log/job.log 2>&1) so a silent failure leaves a trace.

Does every 5 minutes from :02 still fire during a daylight-saving change?
Yes, with a caveat. When clocks spring forward the skipped wall-clock times simply do not occur that day, and when they fall back an hourly job can run twice. For jobs where a double run is harmful, guard the body with a lock file or an idempotency key rather than relying on cron to fire exactly once.

Other schedules in the library