ForHosting KIT · Dates & time

Orthodox Christmas date

Orthodox Christmas falls on 7 January 2026, because it keeps 25 December of the Julian calendar, which runs 13 days behind. Enter a year from 1900 to 2099 and get the celebration on the calendar you use every day. Free in your browser.

Free
Runs in your browser
No sign-up
Your data stays on your device

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

Worked example

If you enter

Year: 2,026

You get

Month: 1
Day: 7
ISO date: 2026-01-07
Calendar: gregorian_observance_of_julian_dec25

Gregorian date of Orthodox Christmas (Julian 25 Dec → 7 Jan, 1900–2099). Search intent: orthodox christmas date. No network calls or random seeds are required. Failed jobs are not billed.

One feast, two calendars

Orthodox Christmas is celebrated on 25 December, but on the Julian calendar, the older system that some churches still use for their feasts. The Gregorian calendar, used for everyday dates, has the same months with the same names, but on any given day the two calendars show different dates. Between 1900 and 2099 the Julian calendar runs exactly 13 days behind. That is why the same named date, 25 December, appears as 7 January on a Gregorian wall calendar. The calculation is a fixed shift of 13 days, so the answer is the same every time you ask.

Getting the year right

The most common slip is entering the wrong year. The celebration belongs to the Christmas season that starts in late December, but on the Gregorian calendar it falls in the first days of January, so the year you enter is the year of that January. For the Christmas observed on 7 January 2026, enter 2026. Another mistake is assuming the 13-day gap holds forever: it is valid from 1900 to 2099, the period this calculator covers. Within that range you can rely on the result for calendars, greetings and teaching material.

What you can do with it

Teaching

Pinned goldens.

FAQ

Why is Orthodox Christmas on 7 January?

Because it is celebrated on 25 December of the Julian calendar. Between 1900 and 2099 the Julian calendar runs 13 days behind the Gregorian one, so its 25 December is our 7 January.

Which year should I enter?

Enter the year of the January in which the celebration falls. The Christmas that follows the end of one year lands in early January of the next, so for 7 January 2026 you enter 2026.

Is the date the same every year?

Yes, within the period this calculator covers. From 1900 to 2099 the gap stays at 13 days, so Orthodox Christmas is always 7 January in the Gregorian calendar; only the year changes.

What does the result include?

The year, the month and the day as separate numbers, plus the full date written as 2026-01-07, ready to paste into a calendar, a spreadsheet or a lesson handout.

Related tools

For developers — API access

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.

API endpoint

POSThttps://api.kit.forhosting.com/date/orthodox-christmas

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.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/date/orthodox-christmas \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"year":2026}'

const res = await fetch("https://api.kit.forhosting.com/date/orthodox-christmas", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "year": 2026
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/date/orthodox-christmas",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "year": 2026
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/date/orthodox-christmas", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"year":2026}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"year":2026}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/date/orthodox-christmas", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "year": 2026
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "date.orthodox_christmas",
  "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.

Pricing

Per request$0.002

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

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Technical notes

The calculator is free in the browser, deterministic, and identical on the API path. Inputs are validated before arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE values when decimals are requested. Use the same JSON from spreadsheets, CMS, automation, or teaching demos.

How it works

Gregorian date of Orthodox Christmas (Julian 25 Dec → 7 Jan, 1900–2099). Fixed +13 day conversion in range. No network calls or random seeds are required. Failed jobs are not billed. No network calls or random seeds are required. Failed jobs are The calculator is free in the browser, deterministic, and identical on the API path. Inputs are validated before arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE values when decimals are requested. Use the same JSON from spreadsheets, CMS, automation, or teaching demos. The calculator is free in the browser, deterministic, and identical on the API path. Inputs are validated before arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE values when decimals are requested. Use the same JSON from spreadsheets, CMS, automation, or teaching demos.

Inputs, limits and rounding

Optional decimals use half-up once. Outputs echo inputs. No network calls or random seeds are required. Failed jobs are not billed. No network calls or random seeds are required. Failed jobs are not billed. Provide required JSON fields. Invalid types raise invalid_input. The calculator is free in the browser, deterministic, and identical on the API path. Inputs are validated before arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE values when decimals are requested. Use the same JSON from spreadsheets, CMS, automation, or teaching demos. The calculator is free in the browser, deterministic, and identical on the API path. Inputs are validated before arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE values when decimals are requested. Use the same JSON from spreadsheets, CMS, automation, or teaching demos.

When to use it

Use when search intent matches. Gregorian date of Orthodox Christmas (Julian 25 Dec → 7 Jan, 1900–2099). No network calls or random seeds are required. Failed jobs are not billed. No network calls or random seeds are required. Failed jobs are not The calculator is free in the browser, deterministic, and identical on the API path. Inputs are validated before arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE values when decimals are requested. Use the same JSON from spreadsheets, CMS, automation, or teaching demos. The calculator is free in the browser, deterministic, and identical on the API path. Inputs are validated before arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE values when decimals are requested. Use the same JSON from spreadsheets, CMS, automation, or teaching demos.

Integration use cases

Quick check

Free widget.

Automation

Same JSON via API.

Technical questions

Free?

Yes tier A.

Network?

No.

Bad input?

invalid_input.

API?

Yes.

Locales?

EN-only; Nitro hydrates.

Read the full KIT documentation →

Run — free