Cron every hour at half past (30 * * * *)

Every hour at half past in cron is 30 * * * * (Unix) or 0 30 * * * ? (Quartz, Spring); next runs are calculated in your browser, in your timezone.

Unix cron (crontab, GitHub Actions, Kubernetes)

30 * * * *

Quartz and Spring (seconds first; valid in both)

0 30 * * * ?

AWS EventBridge (minute first, year last)

cron(30 * * * ? *)

Read by our parser as: Every hour, at 30 minutes past the hour. Open in the cron checker

Next 10 runs

Calculating in your browser...

At a glance

Accepts: Nothing to enter - the schedule is preset on the page
Outputs: The expression in Unix, Quartz/Spring and AWS form, plus its next 10 run times
Where it runs: Entirely in your browser, on your device
What leaves your device: Nothing - what you type stays in this tab
Limits: Run times use your browser's timezone or UTC; real schedulers can start a run late
Account: Not required - there is no sign-up
Price: Free, with no watermark and no usage cap
Made by: Visrut

What it means

30 * * * * runs once an hour, at 30 minutes past: 1:30, 2:30, 3:30. It's still hourly, just offset. The first field is the minute to run at, so any number from 0 to 59 gives you an hourly job at that minute.

When this is the right schedule

Use it when you want an hourly job but not at :00, where shared schedulers and APIs are busiest, or you need it to run after another job that starts on the hour.

When to pick something else

Look elsewhere when you meant "every 30 minutes". That's */30 * * * *, which runs at both :00 and :30.

Things to watch

30 * * * * versus /30 * * *

These are easy to confuse. 30 is a single value (once an hour, at :30). */30 is a step (twice an hour, at :00 and :30).

Chaining after an on-the-hour job

If job A runs at 0 * * * * and usually takes ten minutes, running job B at 30 * * * * leaves a buffer. It's not a real dependency, though; if A ever runs long, B will still start. Use a workflow tool when order matters.

Half-hour timezones

In India (UTC+5:30) or Newfoundland (UTC-3:30), 30 past the hour in UTC lands on the hour locally. If your server is on UTC and you think in local time, check the next runs here with the UTC toggle.

Frequently asked questions

How do I run every hour at 15 minutes past?

15 * * * *. The minute field is the minute past the hour, and * in the hour field repeats it every hour.

Does 30 * * * * run at 12:30 AM?

Yes. The hour field is *, so it covers 0 through 23, including 00:30.