Cron for every Saturday at 2am
A common maintenance window. Note that 02:00 is exactly the hour daylight-saving transitions move, so this run can be skipped or repeated twice a year outside UTC.
0 2 * * 6
At 02:00, on Saturday
Interpreted in UTC · approximately 4.3 runs per month
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
- Minute
0 - At minute 0.
- Hour
2 - At 02:00.
- Day of month
* - Every day of the month.
- Month
* - Every month.
- Day of week
6 - On Saturday.
Next runs
- Sat, 2026-09-05, 02:00
- Sat, 2026-09-12, 02:00
- Sat, 2026-09-19, 02:00
- Sat, 2026-09-26, 02:00
- Sat, 2026-10-03, 02:00
- Sat, 2026-10-10, 02:00
- Sat, 2026-10-17, 02:00
- Sat, 2026-10-24, 02:00
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%202%20*%20*%206'