Every 2 Minutes Cron Expression

*/2 * * * *

Try it live

Valid
MINMinute
0
HRHour
9
DOMDay of Month
*
MONMonth
*
DOWDay of Week
1-5

In plain English

At 09:00 AM, Monday through Friday

English → Cron

Try: "every 5 minutes", "every weekday at 9am", "every Monday at 3pm", "every month on the 1st"

Next 10 Executions

UTC
  1. 1Tue, Jul 7, 09:00 AM UTCin 15h
  2. 2Wed, Jul 8, 09:00 AM UTCin 2d
  3. 3Thu, Jul 9, 09:00 AM UTCin 3d
  4. 4Fri, Jul 10, 09:00 AM UTCin 4d
  5. 5Mon, Jul 13, 09:00 AM UTCin 7d
  6. 6Tue, Jul 14, 09:00 AM UTCin 8d
  7. 7Wed, Jul 15, 09:00 AM UTCin 9d
  8. 8Thu, Jul 16, 09:00 AM UTCin 10d
  9. 9Fri, Jul 17, 09:00 AM UTCin 11d
  10. 10Mon, Jul 20, 09:00 AM UTCin 14d
crontab entrybash
# Add to crontab with: crontab -e
0 9 * * 1-5    /path/to/your/script.sh

When to use this schedule

  • Polling an external API that enforces a 2-minute rate limit
  • Checking for new messages in a queue with low-latency requirements
  • Rotating or flushing in-memory caches before they grow stale
  • Lightweight availability checks on an endpoint that doesn't need per-minute precision

Platform Syntax Comparison

The same "Every 2 Minutes" schedule expressed in every major platform's cron syntax.

PlatformExpression
Standard Linux/Unix
*/2 * * * *
GitHub Actions
*/2 * * * *
Google Cloud Scheduler
*/2 * * * *
Kubernetes CronJob
*/2 * * * *
Azure Functions (NCRONTAB)
0 */2 * * * *
AWS EventBridge
*/2 * * * ? *
Quartz Scheduler
0 */2 * * * ?
Spring @Scheduled
0 */2 * * * *
Jenkins
*/2 * * * *
Apache Airflow
*/2 * * * *

Frequently Asked Questions

Does */2 run at :00, :02, :04... or at some other offset?
Yes — "*/2" in the minute field means every even minute: 0, 2, 4, 6 ... 58. It always aligns to the start of the hour.
What if I want it to run at :01, :03, :05 instead?
Use "1-59/2" in the minute field to start at an odd offset.
Built & maintained by Danny Vargas
Last updated January 2026·Parsing runs in your browser — no expression leaves your device

Related Expressions