Common Schedules
Weekdays at 6:30 PM
End of business day. This page shows you how to implement this cron schedule with detailed examples and execution times.
1
Runs per day
10
Next executions
13
Expression length
Cron Expression
30 18 * * 1-5
Human Readable
Every weekday at 6:30 PM
Field Breakdown
| Field | Value | Meaning |
|---|---|---|
| Minute | 30 | When during the hour (0-59) |
| Hour | 18 | What hour of the day (0-23) |
| Day | * | What day of the month (1-31) |
| Month | * | What month (1-12) |
| Day of Week | 1-5 | What day of the week (0-7, 0=Sunday) |
Next 10 Execution Times
2026-07-28 18:30:00 UTC
2026-08-04 18:30:00 UTC
2026-08-11 18:30:00 UTC
2026-08-18 18:30:00 UTC
2026-08-25 18:30:00 UTC
2026-09-01 18:30:00 UTC
2026-09-08 18:30:00 UTC
2026-09-15 18:30:00 UTC
2026-09-22 18:30:00 UTC
2026-09-29 18:30:00 UTC
Note: Times shown in UTC. Adjust for your local timezone as needed.
Implementation Examples
Linux Crontab
30 18 * * 1-5 /path/to/your/script.sh
Add this line to your crontab file using crontab -e
Docker Compose
services:
cron-job:
image: your-app:latest
command: |
sh -c 'echo "30 18 * * 1-5 /app/script.sh" | crontab - && crond -f'
Kubernetes CronJob
apiVersion: batch/v1
kind: CronJob
metadata:
name: weekdays-at-630-pm
spec:
schedule: "30 18 * * 1-5"
jobTemplate:
spec:
template:
spec:
containers:
- name: job
image: your-app:latest
command: ["/app/script.sh"]
restartPolicy: OnFailure
GitHub Actions
name: Weekdays at 6:30 PM
on:
schedule:
- cron: '30 18 * * 1-5'
jobs:
run:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run task
run: ./script.sh
Common Use Cases
End of business day
- • System maintenance and updates
- • Regular data synchronization
- • Automated reporting and notifications
- • Health checks and monitoring
Test This Expression
Use our free cron tools to test and validate this expression:
Learn More About Cron
Understand the syntax and patterns behind this expression:
More Common Schedules Examples
Every day at midnight
Daily backup or maintenance
0 0 * * *
Every weekday at 9 AM
Business hours notification
0 9 * * 1-5
Every 15 minutes
Frequent monitoring check
*/15 * * * *
Every 2 hours
Regular sync or update
0 */2 * * *
Every Monday at 6:30 AM
Weekly report generation
30 6 * * 1
Every day at noon
Midday status check
0 12 * * *