Cron Translator

Cron for every 3 hours

Eight runs a day: 00:00, 03:00, 06:00, and so on.

0 */3 * * *

At minute 0 past every 3rd hour

Interpreted in UTC · approximately 8 runs per day

Things to check

Note
Interpreted in UTC
A cron expression has no timezone of its own — the scheduler's zone decides when it fires. These times are computed in UTC. The same expression on a host in another zone runs at a different moment.
Fix: Set the schedule timezone explicitly (TZ= or CRON_TZ= in crontab, `timeZone` in Kubernetes, or the scheduler's own setting). Vercel Cron Jobs always run in UTC.

Fields

Minute0: At minute 0.
Hour*/3: Every 3 hours.
Day of month*: Every day of the month.
Month*: Every month.
Day of week*: Every day of the week.

Next runs

Sun, 2026-10-18, 00:002026-10-18T00:00:00.000Z
Sun, 2026-10-18, 03:002026-10-18T03:00:00.000Z
Sun, 2026-10-18, 06:002026-10-18T06:00:00.000Z
Sun, 2026-10-18, 09:002026-10-18T09:00:00.000Z
Sun, 2026-10-18, 12:002026-10-18T12:00:00.000Z
Sun, 2026-10-18, 15:002026-10-18T15:00:00.000Z
Sun, 2026-10-18, 18:002026-10-18T18:00:00.000Z
Sun, 2026-10-18, 21:002026-10-18T21:00:00.000Z

Try a different expression or timezone

Times above are in UTC. Pick a timezone here to see this schedule in local time.

Call this from code or an agent

curl 'https://crontoenglish.com/api/v1/explain?expression=0%20*%2F3%20*%20*%20*'

API and MCP setup · this page as markdown

Related schedules