Tabular Eid al-Adha date
In Hijri year 1445, 10 Dhu al-Hijjah falls on Monday 17 June 2024 under the tabular Islamic calendar. Enter a Hijri year to get the calculated Gregorian date of Eid al-Adha and its weekday, then confirm the observed date with your local authority. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Hijri year
- 1,445
- Hijri date
- 1445-12-10
- Gregorian date
- 2024-06-17
- Gregorian year
- 2,024
- Gregorian month
- 6
Eid al-Adha begins on 10 Dhu al-Hijjah, but a Gregorian date cannot be derived from the Hijri year alone unless a calendar convention is chosen. This calculator uses the arithmetic Islamic civil calendar, also called the tabular Islamic calendar, and maps its result to the proleptic Gregorian calendar. Enter one Hijri year to receive an ISO-style Gregorian date, numeric components, the weekday, and an explicit calendar label. The calculation is deterministic in UTC-style calendar terms: it uses no system clock, location, network lookup, randomness, or crescent-sighting forecast.
What a tabular Eid al-Adha date means
Eid al-Adha is fixed at the tenth day of Dhu al-Hijjah, the twelfth month of the Islamic calendar. The difficult part is mapping that Hijri day onto a Gregorian date, because not every Islamic calendar establishes month boundaries in the same way. This capability chooses the arithmetic Islamic civil convention.
In that convention, months alternate between thirty and twenty-nine days, with an extra day assigned according to a repeating thirty-year leap cycle. That definition makes every date calculable from the year, month, and day without observing the Moon or consulting a published authority. A result is therefore the Gregorian counterpart of 10 Dhu al-Hijjah under this mathematical convention.
It should not be presented as proof of the locally observed festival date, because communities, countries, and calendar providers may establish Dhu al-Hijjah through sightings or a different calculated convention.
Use the result with the right expectations
For example, a developer can generate a stable series of candidate Eid al-Adha dates across many Hijri years, save the declared calendar variant beside every record, and reproduce the series later without depending on a third-party service. It is also useful when comparing calendar algorithms: tabular output gives a fixed baseline against which an observational calendar or another calculated calendar can be checked.
For travel, worship, public-holiday compliance, event announcements, payroll closures, or other decisions tied to an officially recognized date, confirm the result with the relevant local religious or civil authority. Their announced date may differ by a day or more because the start of Dhu al-Hijjah may be determined from crescent observation, jurisdictional policy, or a calculation rule with a different epoch or month structure.
What you can do with it
Compare Islamic calendar conventions
Use the tabular result as a fixed baseline when evaluating observational dates or output from another calculated calendar.
Create historical teaching tables
Map 10 Dhu al-Hijjah across Hijri years for lessons about calendar epochs, leap cycles, and Gregorian conversion.
FAQ
Is this the officially observed Eid al-Adha date?
Not necessarily. It is the date produced by the arithmetic Islamic civil calendar. Confirm official or religious observance with the relevant authority.
Which Hijri date is converted?
The calculator always converts 10 Dhu al-Hijjah, the calendar date of Eid al-Adha, for the supplied Hijri year.
Why can the result differ from a published calendar?
Published calendars may use crescent sightings, jurisdictional announcements, or a different calculated Islamic calendar convention.
How does the tabular Islamic calendar work?
Its months alternate between 30 and 29 days, and an extra day is added on a repeating thirty-year leap cycle. Every date can be worked out from the year, month and day alone, without observing the Moon.
What is a tabular Eid al-Adha date useful for?
It gives a fixed baseline: a stable series of dates across many Hijri years, handy for teaching tables or for checking an observational or other calculated calendar against it. For official decisions, confirm with the local authority.
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
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/eid-al-adha-tabular \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"hijri_year":1445}'const res = await fetch("https://api.kit.forhosting.com/date/eid-al-adha-tabular", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"hijri_year": 1445
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/date/eid-al-adha-tabular",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"hijri_year": 1445
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/date/eid-al-adha-tabular", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"hijri_year":1445}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"hijri_year":1445}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/date/eid-al-adha-tabular", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"hijri_year": 1445
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "date.eid_al_adha_tabular",
"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
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
What a tabular Eid al-Adha date means
The response deliberately includes the calendar value tabular_islamic_civil so stored results retain that essential context.
How the deterministic conversion works
The calculator fixes the Islamic month and day at 12 and 10, counts elapsed days from the arithmetic Islamic epoch, and applies the standard leap-day expression for the tabular thirty-year cycle. It converts the resulting Julian day number to a proleptic Gregorian year, month, and day using bounded integer arithmetic. Supply hijri_year as an integer from 1 through 9999. The output provides gregorian_date in a YYYY-MM-DD style, separate Gregorian components, the corresponding weekday, the original Hijri year, and hijri_date for convenient auditing. Missing values, fractional numbers, strings, non-finite values, zero, negative years, and years above the documented limit return invalid_input instead of being silently coerced. Each successful API call costs $0.002.
Use the result with the right expectations
Treat this endpoint as an exact implementation of one named calendar, not as a forecast of local observance.
Integration use cases
Build reproducible calendar fixtures
Generate stable Eid al-Adha test dates for applications that explicitly implement the arithmetic Islamic civil calendar.
Technical questions
Does the server time zone affect the answer?
No. The conversion uses pure arithmetic and no Date object, clock, locale, daylight-saving rule, or network service.
What does the API request cost?
A successful API request costs $0.002. The interactive browser calculation is free.