DevToolPal
EN

Cron expression

Every 6 hours

Runs four times a day at 00:00, 06:00, 12:00 and 18:00.

0 */6 * * * Open in Cron Expression Parser

Field by field

Field Value Matches
Minute 0 0
Hour */6 0, 6, 12, 18
Day of month * Every value
Month * Every value
Day of week * Every value

Next run times

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

  1. Thu, Jan 1, 2026, 06:00
  2. Thu, Jan 1, 2026, 12:00
  3. Thu, Jan 1, 2026, 18:00
  4. Fri, Jan 2, 2026, 00:00
  5. Fri, Jan 2, 2026, 06:00
  6. Fri, Jan 2, 2026, 12:00

Ready-to-use versions

crontab
0 */6 * * * /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-6-hours
spec:
  schedule: "0 */6 * * *"
  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: '0 */6 * * *'
  workflow_dispatch:

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

Quartz
0 0 */6 * * ?

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 0 */6 * * *")

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

FAQ

› Is 0 */6 * * * the same as 0 0,6,12,18 * * *?

Yes, both match the same four hours.

› Which time zone does 0 */6 * * * 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 0 */6 * * * 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.