ForHosting KIT · Developer Utilities

Weekday of New Year's Day

This New Year's Day weekday calculator takes an explicit ISO date, uses its four-digit year, and tells you which weekday January 1 falls on in that year.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Runs in your browser. Free, unlimited — your data never leaves this page.

The result is derived entirely from the supplied date under Gregorian calendar rules, so it does not depend on the current date, a server clock, a browser timezone, or an external calendar service. Along with the weekday name, the response includes its ISO weekday number and the exact January 1 date used in the calculation.

Use any date to identify the relevant year

Enter one explicit calendar date in the ISO form YYYY-MM-DD. The calculator validates the complete date, including the number of days in its month and the special February rule for leap years, then takes the year portion as the year to evaluate. For example, an input in August 2026 asks a different question from the weekday of that August date: the calculation deliberately returns the weekday for January 1, 2026. This makes the tool convenient when a record, deadline, invoice, or event already contains a date and you need information about the beginning of that same year. Requiring a complete, valid date also prevents ambiguous inputs such as 03/04/26, whose month and day depend on regional convention. Years are accepted from 0001 through 9999, using the proleptic Gregorian calendar consistently across that range. The output repeats the accepted input, identifies the extracted year, and provides the normalized New Year's Day date so the basis of the answer remains visible rather than implicit.

Understand the deterministic weekday calculation

The calculation counts the days in all complete years before the supplied year. Ordinary years contribute 365 days, while leap years contribute one additional day according to the Gregorian rule: a year divisible by four is a leap year unless it is divisible by one hundred, except that years divisible by four hundred remain leap years. The total is reduced modulo seven, using Monday as ISO weekday 1 and Sunday as ISO weekday 7. That arithmetic directly identifies the weekday on which January 1 begins. No system clock, locale setting, timezone database, random value, network request, or JavaScript Date object participates in the result. Consequently, the same valid input produces the same JSON response in an API worker, a browser in another country, or a test process configured with a different timezone. The response includes both a readable English weekday name and the ISO weekday number, making it useful for display while retaining a compact numeric value for sorting, branching, or integration with systems that already follow ISO weekday conventions.

Apply the result in planning and automation

Knowing the weekday of January 1 helps explain how a calendar year aligns with recurring weekly schedules. It can support annual planner generation, reporting-period setup, archival checks, rota templates, and simple calendar trivia. In an automated workflow, send the date already associated with a record and use the returned ISO weekday number to choose a layout or schedule branch. A result of 6 or 7 indicates that New Year's Day is on a weekend under the common Monday-to-Friday working pattern, while values 1 through 5 place it on a weekday; the capability reports calendar facts and does not assume which days your organization treats as working days or holidays. Historical users should also note that the calculation applies Gregorian rules backward for consistency, even for places and years that historically used another civil calendar. The browser execution is available without charge, while an API request costs $0.002. Because the output is determined from the input alone, it is also suitable for reproducible builds, cached reports, regression fixtures, and auditable data transformations.

Build an annual planner

Choose the correct weekday column for January 1 before generating the remaining weeks of a yearly calendar.

Classify a year boundary

Use the ISO weekday number to determine whether New Year's Day begins on a conventional workday or weekend.

Verify archived calendars

Compare the computed January 1 weekday with a historical report or imported calendar record under consistent Gregorian rules.

What date format should I send?

Send a complete ISO calendar date in YYYY-MM-DD form, such as 2026-08-07.

Does the month or day affect the answer?

They must form a valid date, but the calculation uses the date's year to evaluate January 1 of that year.

Does timezone affect the result?

No. The calculation uses integer Gregorian calendar arithmetic and never converts the input into a local timestamp.

How are leap years handled?

Years divisible by four are leap years, century years are not, and years divisible by four hundred are leap years.

What does it cost?

It runs free in your browser. Each API request costs $0.002.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/date/weekday-of-new-year

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/date/weekday-of-new-year \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-08-07"}'
{
  "date": "2026-08-07"
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "date.weekday_of_new_year",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →