Cron expression
*/10 16 21 FEB *
Every 10 minutes, between 16:00 and 16:59, on day 21 of the month, only in February.
Next runs · UTC
- —
- —
- —
- —
- —
September 2026 · UTC
0 runs
Read more in the dedicated guide: Cron every 10 minutes.
What this cron means, field by field
Each field of */10 16 21 FEB * 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 | */10 | every 10 minutes | 0-59. The minute(s) of the hour the job will fire. |
| hour | 16 | at hour 16 | 0-23. The hour(s) of the day the job will fire (0 = midnight, 23 = 11 PM). |
| day of month | 21 | at day of month 21 | 1-31. The day(s) of the month. Use * if you want every day. |
| month | FEB | at month FEB | 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
- Sun 21 Feb · 16:00in 158d 2h
- Sun 21 Feb · 16:10
- Sun 21 Feb · 16:20
- Sun 21 Feb · 16:30
- Sun 21 Feb · 16:40
Similar cron expressions
Common variations and tweaks of */10 16 21 FEB *.
*/5 16 21 FEB *Every 5 minutes, between 16:00 and 16:59, on day 21 of the month, only in February*/20 16 21 FEB *Every 20 minutes, between 16:00 and 16:59, on day 21 of the month, only in February*/10 16 21 FEB 1-5Every 10 minutes, between 16:00 and 16:59, on day 21 of the month, Monday through Friday, only in February
Where else this cron could be used
The same expression */10 16 21 FEB * 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-5Weekdays 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 `*/10 16 21 FEB *` mean?
every 10 minutes, between 16:00 and 16:59, on day 21 of the month, only in February.
When does `*/10 16 21 FEB *` run next?
The next runs (UTC): 2027-02-21 16:00; 2027-02-21 16:10; 2027-02-21 16:20; 2027-02-21 16:30; 2027-02-21 16:40.
Is `*/10 16 21 FEB *` a valid cron expression?
Yes - CronTool's parser accepts this expression and the calendar projects future runs successfully.
Run this cron in production
Stop pasting `*/10 16 21 FEB *` into a host you also have to babysit.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
1.9k+ teams · Free forever tier · No credit card