Cron expression
Weekends at 10 AM
0 10 * * 0,6
Runs at 10:00 on Saturday and Sunday.
Runs per month
≈ 9
Next run (UTC)
Sat 10:00
On CronEngine
Runs on the free plan
What each part means
| Minute | 0 | at minute 0 |
| Hour | 10 | at hour 10 |
| Day of month | * | every day of the month |
| Month | * | every month |
| Day of week | 0,6 | on Sunday and Saturday |
Next runs
- 1 Saturday 24 October 2026 10:00 UTC
- 2 Sunday 25 October 2026 10:00 UTC
- 3 Saturday 31 October 2026 10:00 UTC
- 4 Sunday 1 November 2026 10:00 UTC
- 5 Saturday 7 November 2026 10:00 UTC
See these in your own timezone, or change the schedule →
Good to know
- Saturday is 6 and Sunday is 0. Writing 6-0 does not work: a range has to go from low to high.
- Weekends are a good moment for heavy jobs that would slow things down for users during the week.
Typical uses: Weekly maintenance, rebuilding search indexes, longer backups.
Copy and paste
0 10 * * 0,6 /path/to/script.sh
on:
schedule:
- cron: '0 10 * * 0,6'
GitHub Actions reads this in UTC, and scheduled runs can start late when GitHub is busy. How to start it on time.
Schedule::command('your:command')->weekends()->at('10:00');
Variations
| 0 3 * * 6 | Saturdays at 03:00 |
| 0 9 * * 1-5 | Weekdays at 09:00 → |
Questions
What is the cron expression for weekends at 10 AM?
0 10 * * 0,6. Runs at 10:00 on Saturday and Sunday.
Can GitHub Actions run weekends at 10 AM?
Yes, with cron: '0 10 * * 0,6'. GitHub Actions reads this in UTC, and scheduled runs can start late when GitHub is busy.