How do I test a cron expression?

Paste your expression into SimpleCronTab to see the next 10 scheduled execution times. This lets you verify the schedule matches your intent.

Why might a cron expression produce no executions?

Impossible dates like February 30th (0 0 30 2 *) or conflicting fields that can never match simultaneously will produce no executions.

Cron Expression Tester

30 9 * * 1-5

Every weekday at 9:30 AM

Next 10 Executions

Times shown in UTC

Mon, May 18, 202609:30
Tue, May 19, 202609:30
Wed, May 20, 202609:30
Thu, May 21, 202609:30
Fri, May 22, 202609:30
Mon, May 25, 202609:30
Tue, May 26, 202609:30
Wed, May 27, 202609:30
Thu, May 28, 202609:30
Fri, May 29, 202609:30

Field Breakdown

30

Minute

9

Hour

*

Day of Month

Every day

*

Month

Every month

1-5

Day of Week

Mon, Tue, Wed, Thu, Fri

About This Schedule

A cron expression tester shows you when a cron job will actually run. Instead of mentally parsing 30 9 * * 1-5 and hoping you got it right, you paste the expression and see: "Monday Mar 23 at 9:30 AM, Tuesday Mar 24 at 9:30 AM, Wednesday Mar 25 at 9:30 AM..."

Testing is critical because cron expressions can be deceptive. For example, 0 0 30 2 * looks like "February 30th" — but February never has 30 days, so this job will never run. A tester catches this immediately by showing no upcoming executions.

SimpleCronTab shows the next 10 execution times for any expression, with timezone support. You can test standard Unix cron, Quartz, AWS, and other formats. The tester updates in real time as you modify the expression.

Frequently Asked Questions

Related Expressions

Cron Expression Validator

0 */4 * * 1-5

View

Cron Expression Generator

*/15 9-17 * * 1-5

View

Cron Expression Translator

0 9,17 * * 1-5

View

Build a custom cron expression