ClockOrbit

Hourly

0 */3 * * *

Run eight times a day, 00:00, 03:00, … 21:00.

This preview is live: the table below shows the actual next run times for 0 */3 * * * in your time zone, recomputed in your browser. Change the expression, dialect, or zone to experiment, then copy the result.

Next runs
valid
Upcoming runs
Fri, Nov 6 2026
15:00 UTC
in 2 hours
Fri, Nov 6 2026
18:00 UTC
in 5 hours
Fri, Nov 6 2026
21:00 UTC
in 8 hours
Sat, Nov 7 2026
00:00 UTC
in 11 hours
Sat, Nov 7 2026
03:00 UTC
in 14 hours
Sat, Nov 7 2026
06:00 UTC
in 17 hours
Sat, Nov 7 2026
09:00 UTC
in 20 hours
Sat, Nov 7 2026
12:00 UTC
in 23 hours
Sat, Nov 7 2026
15:00 UTC
in 26 hours
Sat, Nov 7 2026
18:00 UTC
in 29 hours
Sat, Nov 7 2026
21:00 UTC
in 32 hours
Sun, Nov 8 2026
00:00 UTC
in 35 hours
Sun, Nov 8 2026
03:00 UTC
in 38 hours
Sun, Nov 8 2026
06:00 UTC
in 41 hours
Sun, Nov 8 2026
09:00 UTC
in 44 hours
Sun, Nov 8 2026
12:00 UTC
in 47 hours
Sun, Nov 8 2026
15:00 UTC
in 2 days
Sun, Nov 8 2026
18:00 UTC
in 2 days
Sun, Nov 8 2026
21:00 UTC
in 2 days
Mon, Nov 9 2026
00:00 UTC
in 2 days
Mon, Nov 9 2026
03:00 UTC
in 3 days
Mon, Nov 9 2026
06:00 UTC
in 3 days
Mon, Nov 9 2026
09:00 UTC
in 3 days
Mon, Nov 9 2026
12:00 UTC
in 3 days
Mon, Nov 9 2026
15:00 UTC
in 3 days

What 0 */3 * * * means

0 */3 * * * fires eight times a day at three-hour intervals starting from midnight. Because 24 divides evenly by 3, the spacing is perfectly regular all the way around the clock, ending at 21:00 and resuming at 00:00.

Three-hour cadence suits jobs that are moderately heavy and tied to a quarter-of-the-day rhythm: think batch imports, periodic full syncs, or recomputing something that changes slowly but materially over the course of a day.

Field-by-field breakdown

Unix cron has five fields. Here is what each one is doing in this expression:

FieldValueMeaning
Minute0minute = 0
Hour*/3every 3 (step) across hour
Day of month*every day-of-month
Month*every month
Day of week*every day-of-week

Every 3 hours in every scheduler

The same cadence written for the seven cron dialects you are most likely to meet. Copy the line for the system you target, the field count and day-of-week numbering differ between them.

SchedulerExpressionCopy
Unix / crontab0 */3 * * *
GitHub Actions0 */3 * * *
Kubernetes CronJob0 */3 * * *
Vercel Cron0 */3 * * *
Quartz0 0 */3 * * * *
Spring0 0 */3 * * *
AWS EventBridge0 */3 * * * *

When you would use 0 */3 * * *

The gotcha worth knowing

Step values in the hour field only divide cleanly for factors of 24 (2, 3, 4, 6, 8, 12). */5 in the hour field fires at 0, 5, 10, 15, 20 then jumps to 0, a 4-hour gap, not 5.

People also search for

cron every 3 hours0 */3 * * *crontab every three hours

0 */3 * * * FAQ

What does the cron expression 0 */3 * * * mean?

0 */3 * * * means: Run eight times a day, 00:00, 03:00, … 21:00. 0 */3 * * * fires eight times a day at three-hour intervals starting from midnight. Because 24 divides evenly by 3, the spacing is perfectly regular all the way around the clock, ending at 21:00 and resuming at 00:00.

How do I write "every 3 hours" in GitHub Actions?

Use 0 */3 * * * in the schedule's cron field. Step values in the hour field only divide cleanly for factors of 24 (2, 3, 4, 6, 8, 12). */5 in the hour field fires at 0, 5, 10, 15, 20 then jumps to 0, a 4-hour gap, not 5.

How do I write "every 3 hours" for AWS EventBridge?

EventBridge uses six fields with a required year and a ? placeholder in one day field: 0 */3 * * * *. Wrap it as cron(0 */3 * * * *) in the console or CloudFormation.

What is the Quartz equivalent of 0 */3 * * *?

Quartz is seconds-first with a trailing year, so the equivalent is 0 0 */3 * * * *. Remember Quartz numbers Sunday as 1, the opposite of Unix.

Related cron patterns

More cron tools

Browse the full set of cron pattern pages, or jump to the interactive tools: the cron expression builder for designing a schedule from scratch, the cron cheat sheet for a side-by-side reference, the cron timezone translator for moving a schedule between zones and dialects, and the GitHub Actions cron picker for DST-stable CI schedules.