Cron expression `2 2 10 JUL *` runs at 02:02, on day 10 of the month, only in July

What this cron means, field by field

Each field of 2 2 10 JUL * controls one dimension of the schedule. Hover over any value in the editor above to see its tooltip; the table below summarises the same information.

Field	Value	Means	Range / hint
minute	`2`	at minute 2	0-59. The minute(s) of the hour the job will fire.
hour	`2`	at hour 2	0-23. The hour(s) of the day the job will fire (0 = midnight, 23 = 11 PM).
day of month	`10`	at day of month 10	1-31. The day(s) of the month. Use * if you want every day.
month	`JUL`	at month JUL	1-12 or JAN-DEC. The month(s). Use * for every month.
day of week	`*`	every value (wildcard)	0-7 or SUN-SAT (0 and 7 both mean Sunday). Use * for every day of the week.

Next 5 runs

Shown in UTC. Change the timezone in the editor.

Next runs · UTC

Sat 10 Jul · 02:02in 296d 16h
Mon 10 Jul · 02:02
Tue 10 Jul · 02:02
Wed 10 Jul · 02:02
Thu 10 Jul · 02:02

Similar cron expressions

Common variations and tweaks of 2 2 10 JUL *.

2 2 10 JUL 1-5At 02:02, on day 10 of the month, Monday through Friday, only in July

Where else this cron could be used

The same expression 2 2 10 JUL * works in:

Standard Unix crontab (5-field syntax).
AWS EventBridge / Lambda Scheduled (with a 6th field for year, often *).
Vercel cron jobs (declared in vercel.json).
Quartz Scheduler and node-cron, robfig/cron and similar libraries.

Examples

0 18 * * *
Every day at 18:00
0 */5 * * *
Every 5 hours
0 18 * * 1-5
Weekdays at 18:00
0 0 1 * *
Once a month, on the 1st at midnight

Cheatsheet

Full cheatsheet

Field	Req.	Range	Wildcards
minute	yes	0-59	, - * /
hour	yes	0-23	, - * /
day of month	yes	1-31	, - * /
month	yes	1-12 or JAN-DEC	, - * /
day of week	yes	0-6 or names; some dialects use 0-7 or 1-7 — see Dialects	, - * /

Frequently asked questions

What does the cron expression `2 2 10 JUL *` mean?

at 02:02, on day 10 of the month, only in July.

When does `2 2 10 JUL *` run next?

The next runs (UTC): 2027-07-10 02:02; 2028-07-10 02:02; 2029-07-10 02:02; 2030-07-10 02:02; 2031-07-10 02:02.

Is `2 2 10 JUL *` a valid cron expression?

Yes - CronTool's parser accepts this expression and the calendar projects future runs successfully.