# 0 */5 * * *

**At minute 0 past every 5th hour**

- Expression: `0 */5 * * *`
- Timezone: UTC
- Frequency: approximately 5 runs per day (5/day)

## Fields

| Field | Value | Meaning |
| --- | --- | --- |
| Minute | `0` | At minute 0. |
| Hour | `*/5` | Every 5 hours. |
| Day of month | `*` | Every day of the month. |
| Month | `*` | Every month. |
| Day of week | `*` | Every day of the week. |

## Next runs (UTC)

- Wed, 2026-09-02, 20:00 — `2026-09-02T20:00:00.000Z`
- Thu, 2026-09-03, 00:00 — `2026-09-03T00:00:00.000Z`
- Thu, 2026-09-03, 05:00 — `2026-09-03T05:00:00.000Z`
- Thu, 2026-09-03, 10:00 — `2026-09-03T10:00:00.000Z`
- Thu, 2026-09-03, 15:00 — `2026-09-03T15:00:00.000Z`

## Warnings

### Step of 5 does not divide 24 hours evenly (caution)

"*/5" fires at 0, 5, 10 and 15, … and last at 20. Because 5 does not divide 24 evenly, the interval from 20 back around to 0 is 4, not 5. The schedule is not truly "every 5 hours".

**Fix:** Use a step that divides 24 evenly, or list the values explicitly.

### Interpreted in UTC (info)

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.

---

Canonical URL: https://crontoenglish.com/cron/every-5-hours
JSON API: `GET https://crontoenglish.com/api/v1/explain?expression=...`
MCP endpoint: `https://crontoenglish.com/api/mcp`