Cron next run times

List the next run times of a cron expression after a given moment, in the time zone you choose.

Input

A five-field cron expression or a macro such as @daily.
Runs are listed strictly after this date and time.
Time zone the schedule runs in.
How many run times to list.

Result

Fill in the input and press Run.

Your input is processed in memory and then discarded. It is not stored or logged. Even so, don't paste live passwords or keys into any online tool.

Use it from code or an agent

curl -s https://setget.net/v1/tools/cron-next-runs \
  -H 'Content-Type: application/json' \
  -d '{"input":{"expression":"0 9 * * 1-5","start":"2026-03-05T10:00","zone":"Europe/Oslo","count":3}}'
import json, urllib.request

body = {'input': {'expression': '0 9 * * 1-5', 'start': '2026-03-05T10:00', 'zone': 'Europe/Oslo', 'count': 3}}
request = urllib.request.Request("https://setget.net/v1/tools/cron-next-runs", json.dumps(body).encode(),
                                 {"Content-Type": "application/json"})
print(json.load(urllib.request.urlopen(request))["result"])
const response = await fetch("https://setget.net/v1/tools/cron-next-runs", {
  method: "POST",
  headers: {"Content-Type": "application/json"},
  body: JSON.stringify({"input":{"expression":"0 9 * * 1-5","start":"2026-03-05T10:00","zone":"Europe/Oslo","count":3}}),
});
console.log((await response.json()).result);
Tool: run_tool
Arguments:
{
  "slug": "cron-next-runs",
  "input": {
    "expression": "0 9 * * 1-5",
    "start": "2026-03-05T10:00",
    "zone": "Europe/Oslo",
    "count": 3
  }
}
{
  "input": {
    "expression": "0 9 * * 1-5",
    "start": "2026-03-05T10:00",
    "zone": "Europe/Oslo",
    "count": 3
  }
}

Endpoint: POST /v1/tools/cron-next-runs. Over MCP: run_tool with slug: "cron-next-runs". Machine-readable: input schema, Markdown. Connect an agent.

Inputs

NameTypeRequiredWhat it does
expression string yes A five-field cron expression or a macro such as @daily.
start string yes Runs are listed strictly after this date and time.
zone string no Time zone the schedule runs in. Default: "UTC".
count integer no How many run times to list. Default: 5. From 1 to 50.

Examples

Input
{
  "expression": "0 9 * * 1-5",
  "start": "2026-03-05T10:00",
  "zone": "Europe/Oslo",
  "count": 3
}
Result
{
  "expression": "0 9 * * 1-5",
  "description": "At 09:00 on Monday to Friday.",
  "zone": "Europe/Oslo",
  "after": "2026-03-05T10:00:00+01:00",
  "runs": [
    "2026-03-06T09:00:00+01:00",
    "2026-03-09T09:00:00+01:00",
    "2026-03-10T09:00:00+01:00"
  ],
  "runs_utc": [
    "2026-03-06T08:00:00Z",
    "2026-03-09T08:00:00Z",
    "2026-03-10T08:00:00Z"
  ],
  "note": null
}

Day of month or day of week

Input
{
  "expression": "0 0 15 * 1",
  "start": "2026-03-01",
  "count": 4
}
Result
{
  "expression": "0 0 15 * 1",
  "description": "At 00:00 on day 15 of the month or on Monday.",
  "zone": "UTC",
  "after": "2026-03-01T00:00:00+00:00",
  "runs": [
    "2026-03-02T00:00:00+00:00",
    "2026-03-09T00:00:00+00:00",
    "2026-03-15T00:00:00+00:00",
    "2026-03-16T00:00:00+00:00"
  ],
  "runs_utc": [
    "2026-03-02T00:00:00Z",
    "2026-03-09T00:00:00Z",
    "2026-03-15T00:00:00Z",
    "2026-03-16T00:00:00Z"
  ],
  "note": null
}

Questions

What happens when both day fields are set?
Standard cron runs when either one matches. "0 0 13 * 5" runs on the 13th and also on every Friday, not only on Friday the 13th. The exception is a day field that starts with *, such as */2: then both must match.
Which syntax is supported?
Five fields with values, lists (1,15), ranges (1-5), steps (*/10, 10-40/5), month and weekday names (JAN, MON), and the macros @yearly, @monthly, @weekly, @daily and @hourly. Seconds, years, L, W and # are not supported.
Why must I send a start time?
So the same request always gives the same answer. Use time-now to get the current time if you want runs from now.
What happens around daylight saving changes?
A run at a clock time that is skipped when clocks go forward does not happen that day. A clock time that occurs twice when clocks go back runs once, the first time. A note is added when a run is skipped.