Counts you can plan capacity with
The calendar view counts runs for every day of the next year and shades the heatmap by volume. The side panel summarises total runs, active days, the minimum and maximum runs per day and the shortest and longest gap between consecutive runs. Counts are exact: on the day clocks change, a schedule that touches the missing or repeated hour has one run more or fewer, and the count reflects the DST policy you selected.
The week × hour grid shows when load lands. Use it to spot jobs that pile up at the top of the hour, or to check that a maintenance window really is quiet.
Budgets and limits
Calculations run in a background worker with a time budget. Very dense schedules (every second) are counted per day arithmetically instead of listing millions of runs; the run list itself is capped at 1,000 entries.
Try these
*/20 8-18 * * 1-5Every 20 min, business hours0 */4 * * *Every 4 hours0 0 12 ? * 2#1,4#3Quartz nth weekdays
Questions
How many times does */5 * * * * run per year?
288 times a day, so 105,120 in a 365-day year in UTC. In a zone with DST, the spring-forward day has 276 runs and the fall-back day 300 under a wall-clock policy.
Why does the shortest gap differ from the step?
Steps restart at each hour or day boundary. */7 minutes runs at :56 and then :00, a four-minute gap. The calculator measures real gaps between instants.