Imsak and Iftar Times Explained

Blog · Prayer and Ramadan · 8 min read · Published 31 August 2026 · Updated 5 September 2026

On most timetables, iftar is the Maghrib time, and imsak is a dawn marker that is either the same instant as Fajr or a few minutes earlier, depending on who published the table. That second half is where the confusion comes from. Two apps can show the same city, the same day, and two different imsak times, and both can be reporting their numbers honestly.

Here is what each label means, why they drift apart, and how to read a timetable without guessing.

Key facts

• Iftar is not a separate calculation. It is the Maghrib time on your timetable.
• Imsak is a dawn marker. Some publishers set it equal to Fajr; some print it a fixed number of minutes earlier as a margin of caution.
• The margin is a publishing convention, not an astronomical event. There is no angle of the sun that defines “ten minutes before Fajr.”
• Fajr itself depends on the calculation method. Muslim World League uses a Fajr angle of 18 degrees; ISNA uses 15; Umm al-Qura uses 18.5. Those are different definitions of the same moment, so they give different clock times.
• When two apps disagree, the cause is almost always method, imsak offset, or rounding, in that order.
• Timing questions about fasting are answered by your local mosque or religious authority, not by a calculator.

What imsak means on a timetable

Imsak is the label publishers use for the end of the pre-dawn period, and on a printed table it sits at the very top of the row, before sunrise.

The practical question is how it relates to Fajr, and the honest answer is that it depends entirely on the publisher.

Turkey’s Diyanet is a good example, because people often assume it prints a gap. Its published timetable does not. The Turkish version of Diyanet’s table has one dawn column labelled İmsak, and the English version of the exact same table labels that column Fajr. Same column, same number, two names. In Diyanet’s convention imsak and Fajr are one instant, and the “gap” some readers expect is not there.

Other publishers do print a gap. A widely used prayer times API, Aladhan, returns a separate Imsak field set ten minutes before Fajr by default. For Istanbul on 31 August 2026 using the Diyanet method, it reports Fajr at 04:52 and Imsak at 04:42. Neither number is invented. The 04:52 comes from a sun angle. The 04:42 comes from a ten minute editorial margin applied on top of it.

So if your friend’s app says 04:42 and yours says 04:52, nobody is wrong. One is showing the calculated dawn, the other is showing dawn minus a cushion.

What iftar means

Iftar is simpler. It is the Maghrib time, the moment the sun has set for your coordinates. Almost every serious timetable derives it the same way, from sunset for your latitude, longitude and elevation.

Small differences still appear, usually for three reasons. Some publishers add a minute or two after sunset before calling it Maghrib. Some round to the nearest minute rather than down. And some apply a small local adjustment set by a national authority. Diyanet, for instance, applies its own offsets to sunrise and Maghrib rather than using raw astronomical sunset.

That is why iftar times across apps typically differ by one to three minutes, while imsak times can differ by ten or more.

Why two apps show a different imsak for the same city

Three variables stack, and each one moves the number:

The first is the calculation method. Fajr and Isha are defined by how far the sun sits below the horizon, because neither moment is visible as a sharp event, and published methods pick different angles. These are the parameters the AlAdhan endpoint returned on 7 September 2026.

The Umm al-Qura row is the odd one, because it does not use an Isha angle at all: Umm al-Qura at Fajr 18.5 with Isha fixed at 90 minutes after Maghrib is a fixed interval rather than a sun position, and it never fails to compute in high summer the way an angle can.

The spread across the column matters more than any single row. A city calculated at 15 degrees will have a noticeably later Fajr than the same city at 20 degrees, and in summer at higher latitudes the gap widens further. Why two apps disagree works through the rest of that arithmetic.

The second is the imsak offset. Zero minutes, five, ten, fifteen. It is a choice, and most apps do not tell you which one they made.

The third is rounding and local adjustment. A minute here, a minute there, plus any tuning a national authority publishes for its own territory.

If you want to compare two apps properly, compare their Fajr values first. If Fajr matches and imsak does not, the difference is purely the offset.

How our city pages label things

We tried to make this boring and legible rather than clever.

On every city page we show the calculated Fajr and Maghrib, and we name the method used to produce them. Nothing is renamed to look more familiar than it is. If a page says Fajr, it is the calculated Fajr for that method, not Fajr minus a cushion.

We do not silently subtract minutes and call the result imsak. If you follow a timetable that prints an imsak margin, you can apply that margin yourself, and you will know exactly what you are applying it to. Hiding an offset inside a number is the thing that makes two apps look like they contradict each other.

You can see how this reads on a real page for Istanbul, Cairo or Kuala Lumpur, or start from the prayer times index and find your own city.

Planning Ramadan with the 30-day table

During Ramadan the useful view is not today. It is the whole month at once, because at Turkish, Central Asian and European latitudes the fasting window shifts by a few minutes a day and the first and last day can be more than an hour apart.

Each city page carries a 30-day table with a hijri date column alongside the Gregorian one. That pairing does the work that a single day view cannot:

• You can see the fasting window widen or narrow across the month at a glance.
• You can line up a specific hijri date with a real calendar date, which is what you actually need when arranging travel, work shifts or a family meal.
• You can check the last ten nights against the Gregorian dates without counting on your fingers.

For the wider picture, including how hijri dates map across the year, see the hijri calendar. The city pages are on this website, not in the Quran Habit app, which reads the Quran and keeps a reading habit and carries no prayer times.

One thing a calculator cannot do

A timetable is astronomy plus a published convention. It is not a ruling. Questions about when your fast begins and ends, which method applies where you live, and whether to observe an imsak margin at all are matters for your local mosque or religious authority. Where your community follows a specific method, use that method and set your app to match it.

What a good timetable owes you is transparency: the method it used, and no hidden minutes.

Sources

• Calculation method parameters: Aladhan methods API and Aladhan calculation methods, cross-checked against PrayTimes calculation methods.
• Diyanet column labelling and the Istanbul figures: Diyanet prayer times for Istanbul, Turkish and English versions, retrieved 31 August 2026.