# 0 0 1 1 *

**At 00:00, on the 1st of the month, in January**

- Expression: `0 0 1 1 *`
- Timezone: UTC
- Frequency: never runs (0/day)

## Fields

| Field | Value | Meaning |
| --- | --- | --- |
| Minute | `0` | At minute 0. |
| Hour | `0` | At 00:00. |
| Day of month | `1` | On the 1st. |
| Month | `1` | In January. |
| Day of week | `*` | Every day of the week. |

## Next runs (UTC)

- Fri, 2027-01-01, 00:00 — `2027-01-01T00:00:00.000Z`
- Sat, 2028-01-01, 00:00 — `2028-01-01T00:00:00.000Z`
- Mon, 2029-01-01, 00:00 — `2029-01-01T00:00:00.000Z`
- Tue, 2030-01-01, 00:00 — `2030-01-01T00:00:00.000Z`
- Wed, 2031-01-01, 00:00 — `2031-01-01T00:00:00.000Z`

## Warnings

### Interpreted in UTC (info)

A cron expression has no timezone of its own — the scheduler's zone decides when it fires. These times are computed in UTC. The same expression on a host in another zone runs at a different moment.

**Fix:** Set the schedule timezone explicitly (TZ= or CRON_TZ= in crontab, `timeZone` in Kubernetes, or the scheduler's own setting). Vercel Cron Jobs always run in UTC.

---

Canonical URL: https://crontoenglish.com/cron/every-year-on-january-1
JSON API: `GET https://crontoenglish.com/api/v1/explain?expression=...`
MCP endpoint: `https://crontoenglish.com/api/mcp`