Cron Translator

Cron for every day at 5pm

Once a day at 17:00, for end-of-day rollups.

0 17 * * *

At 17:00

Interpreted in UTC · approximately 1 run 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.
Hour17: At 17:00.
Day of month*: Every day of the month.
Month*: Every month.
Day of week*: Every day of the week.

Next runs

Wed, 2026-09-02, 17:002026-09-02T17:00:00.000Z
Thu, 2026-09-03, 17:002026-09-03T17:00:00.000Z
Fri, 2026-09-04, 17:002026-09-04T17:00:00.000Z
Sat, 2026-09-05, 17:002026-09-05T17:00:00.000Z
Sun, 2026-09-06, 17:002026-09-06T17:00:00.000Z
Mon, 2026-09-07, 17:002026-09-07T17:00:00.000Z
Tue, 2026-09-08, 17:002026-09-08T17:00:00.000Z
Wed, 2026-09-09, 17:002026-09-09T17: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%2017%20*%20*%20*'

API and MCP setup · this page as markdown

Related schedules