Cron Job Every weekend at 9 AM

Run a cron job every Saturday and Sunday at 9:00 AM. Use the cron string 0 9 * * 6,0, see the next 5 execution times, and copy Python, Node.js, Bash and n8n snippets.

Quick Answers

What does the "Every weekend at 9 AM" cron expression mean?
This cron expression is "0 9 * * 6,0", which in plain English means: Run a cron job every Saturday and Sunday at 9:00 AM..
When will this cron expression run next?
With the expression "0 9 * * 6,0", the next execution times are Sat, Aug 15, 2026, 09:00:00 AM UTC, Sun, Aug 16, 2026, 09:00:00 AM UTC, Sat, Aug 22, 2026, 09:00:00 AM UTC.
How do I use this cron expression?
Copy the exact string into crontab, cron triggers, or any scheduler such as GitHub Actions, n8n or Docker. Pre-built code snippets for Python, Node.js, Bash, Docker, GitHub Actions and n8n are included on this page.
Explore the full Cron Cheat Sheet with all 50 schedules
Cron Expression
Copy this exact string into crontab, cron triggers, or schedulers.
0 9 * * 6,0

Human readable

Run a cron job every Saturday and Sunday at 9:00 AM.

Next 5 execution times

  1. 1Sat, Aug 15, 2026, 09:00:00 AM UTC
  2. 2Sun, Aug 16, 2026, 09:00:00 AM UTC
  3. 3Sat, Aug 22, 2026, 09:00:00 AM UTC
  4. 4Sun, Aug 23, 2026, 09:00:00 AM UTC
  5. 5Sat, Aug 29, 2026, 09:00:00 AM UTC
Python
from crontab import CronTab
from datetime import datetime

# Install: pip install python-crontab
cron = CronTab(user=True)
job = cron.new(command="/usr/bin/python3 /var/www/job_every-weekend-at-9am.py", comment="scheduled by crongen")
job.setall("0 9 * * 6,0")
cron.write()

print(f"Installed: 0 9 * * 6,0 -> /usr/bin/python3 /var/www/job_every-weekend-at-9am.py")

About the "every weekend at 9 AM" cron schedule

The "every weekend at 9 AM" cron schedule uses the expression "0 9 * * 6,0". This schedule fires 2 times per week.

In plain English the cron string "0 9 * * 6,0" means: At 09:00 AM, only on Sunday and Saturday.

This cadence is a common choice for weekend-only jobs such as full backups or overnight batch reporting. The schedule is deliberately kept simple: copy the string into any cron-aware scheduler (crontab, Vercel Cron, GitHub Actions, n8n, Docker or Kubernetes CronJob) and the run will repeat automatically — steady, with no manual triggering.

Frequently asked questions