Nirnay Engine · Grahan

Why the “9 hours” and “12 hours” before an eclipse don’t match the eclipse times

ગ્રહણ વેધ — ૩ પ્રહર (ચંદ્ર) અને ૪ પ્રહર (સૂર્ય)

A common question: we’re told not to eat for 9 hours before a lunar eclipse and 12 hours before a solar one — but when you check the published eclipse times, the gap is never actually 9 or 12 hours. Here is why, with the real numbers.

The short answer

“9 hours” and “12 hours” are not clock hours. They are 3 and 4 prahars — watches of the day and night that stretch and shrink with the season and with how far north you live.

Three things then push the real gap away from 9 and 12:

  1. A prahar is a quarter of the daytime (or a quarter of the night), not a fixed 3 hours. In Bolton it runs from 1h 49m to 4h 10m — and both of those extremes occur on the same midsummer day.
  2. The fast starts at the beginning of a prahar, not at “eclipse minus N hours”. That adds up to a whole extra prahar on top.
  3. It is measured from first contact at your location — not from the headline “maximum eclipse” time, and not from India’s times.

So 9 and 12 are a memory aid, not the calculation. The engine computes the real boundary.

1 What the rule actually says

The pre-eclipse period is Vedha (વેધ). During it, food is not taken — Vedha and the eclipse food-stop are the same boundary. Its length is given in prahars (also called yam), not in hours:

EclipseVedha lengthCounted back through
Solar (સૂર્ય ગ્રહણ)4 praharsthe prahar containing first contact
Lunar (ચંદ્ર ગ્રહણ)3 praharsthe prahar containing first contact

And a prahar is defined by sunrise and sunset at your own location:

day prahar   = (sunset − sunrise) ÷ 4
night prahar = (next sunrise − sunset) ÷ 4

// Day is divided into 4 watches, night into 4 watches.
// They are equal to each other only at the equinox.

2 So where do 9 and 12 come from?

From the nominal prahar. A full day-and-night is 24 hours, divided into 8 watches, so a prahar is loosely quoted as 3 hours. On that reckoning:

EclipsePrahars× 3 hoursBecomes the saying
Lunar39h“no food for 9 hours”
Solar412h“no food for 12 hours”

That arithmetic is only exact when day and night are both exactly 12 hours long — i.e. at the equinox. Every other day of the year, a prahar is not 3 hours, and the saying drifts from the actual rule. The further from the equator you are, the more it drifts.

3 Reason one — prahars stretch and shrink

Two real days at the same place (Bolton, UK), as computed by the engine:

DateDay praharNight prahar
12 August 2026 (summer)3h 45m2h 15m
31 December 2028 (winter)1h 53m4h 07m
Same town, same rule — the “3-hour” prahar is anywhere from under 2 hours to over 4.

A solar eclipse asks for four prahars. In Bolton in summer, four day prahars come to 15h 00m. In winter they come to 7h 32m. Neither is 12.

4 Reason two — it starts at a boundary, not a countdown

This is the part that surprises most people, and it is the single biggest reason the numbers don’t line up. You do not subtract 4 prahars from the eclipse time. The procedure is:

1. Find which prahar the eclipse’s first contact falls in.
2. Count back 4 prahars (solar) or 3 prahars (lunar).
3. The fast begins at the start of that prahar.

Because you land on the start of a watch, the gap always also includes however much of the contact prahar had already run before the eclipse began. That is an extra 0 to 1 whole prahar on top of the nominal 3 or 4 — and it varies with every eclipse.

5 Reason three — first contact, not maximum

Published tables usually headline the maximum of the eclipse, because that is the photogenic moment. The rule anchors on first contact (sparsha) — the instant the shadow first touches the disc. For today’s eclipse that is a difference of 57 minutes. Measuring back from the wrong anchor shifts everything by that much again.

6 Worked example — the solar eclipse of 12 August 2026

Computed for Bolton, UK. Sunrise 05:44, sunset 20:45 (BST) — a long summer day, so day prahars are long (3h 45m) and night prahars are short (2h 15m).

First contact is at 18:13, which falls in Day Prahar 4. Counting back four prahars — Day P3, Day P2, Day P1, then the previous Night P4 — the fast begins at the start of that night watch: 03:29.

Night P4 Day P1 Day P2 Day P3 Day P4 ← 4 ← 3 ← 2 ← 1 03:29 05:44 09:29 13:15 17:00 20:45 sunrise sunset 18:13 first contact Vedha — no food · 14h 44m the saying would predict 12h 00m

Where the 14h 44m comes from

SegmentLength
Previous Night Prahar 4  (03:29 → 05:44)2h 15m
Day Prahars 1, 2 and 3  (05:44 → 17:00)11h 16m
Part of Day Prahar 4 already elapsed  (17:00 → 18:13)1h 13m
Total from food-stop to first contact14h 44m
What “12 hours” would have predicted12h 00m
Out by 2h 44m — and none of it is an error. It is the rule working correctly.

Notice the third row. Even if every prahar had been exactly 3 hours, you would still not get 12, because the fast begins at the start of Day Prahar 4 — well over an hour before the eclipse touched anything.

7 Reason four — it is your sunrise, not India’s

Prahars are built from local sunrise and sunset, so the same eclipse gives a different food-stop in different cities. And there is a prior question: if the eclipse is not visible where you are, Vedha and Sutak do not apply at all (no Rahu-darshan). The engine checks visibility first, before it computes any timing.

CityVisible?First contactFood-stopGap
Bolton, UKYes18:13 BST03:29 BST14h 44m
Madrid, SpainYes19:36 CEST04:51 CEST14h 45m
Ahmedabad, IndiaNoNot visible — no Vedha, no Sutak
Solar eclipse of 12 August 2026. Times in each city’s own local clock.
This is why a printed “9 / 12 hours before” note can mislead. Reproduced from an Indian almanac, it can tell someone in the UK to fast for an eclipse that never rises there — or give them a time that is hours out for the one that does.

8 How far off is the saying, in practice?

Every visible eclipse for Bolton, UK over the next six years, straight from the engine:

DateTypeRule of thumbActual VedhaDifference
12 Aug 2026Solar12h14h 44m+2h 44m
2 Aug 2027Solar12h11h 59m−1m
12 Jan 2028Lunar9h13h 30m+4h 30m
26 Jan 2028Solar12h11h 21m−39m
31 Dec 2028Lunar9h7h 26m−1h 34m
20 Dec 2029Lunar9h8h 48m−12m
1 Jun 2030Solar12h8h 03m−3h 57m
The error swings both ways, from nearly 4 hours short to about 4½ hours long. For the lunar rows the contact point is the moment the eclipsed moon actually becomes visible, which on 31 Dec 2028 is moonrise — the eclipse starts below the horizon.

Two rows are worth a second look.

2 August 2027 lands on 11h 59m 54s — six seconds under the “12 hours”. That is a coincidence, not a confirmation. The day prahar that morning happens to be 3h 55m and first contact happens to fall early in Day Prahar 1, and the two errors cancel. Change the date or the town and the agreement disappears.

1 June 2030 is the opposite. The solar Vedha is 8h 03m — shorter than the lunar “9 hours”, even though solar is the longer rule at 4 prahars. First contact is just after sunrise, so the count runs back through four short midsummer night watches of 1h 49m each. The shorthand cannot express that; the prahar rule handles it without any special case.

9 The concession for those who cannot fast

For children, the elderly and the unwell, the lookback is one prahar rather than the full three or four. Everything else about the procedure is unchanged — and that includes section 4: you do not subtract one prahar from first contact. You find the prahar containing first contact, step back one watch, and begin at the start of that watch. The food-stop lands on a boundary here exactly as it does for the full Vedha; no food-stop ever falls mid-watch.

For the 12 August 2026 eclipse in Bolton, first contact at 18:13 sits in Day Prahar 4. One watch back is Day Prahar 3, which begins at 13:14 — that is the concession time, against 03:29 for everyone else. Note it is 4h 59m before contact, not 3h 45m: the same “extra part-prahar” from section 4 applies, so even the concession is longer than one bare prahar.

And when they may eat again

The concession is symmetric — it shortens the fast at both ends. Ordinarily everyone eats again at the eclipse release (moksha), after snan. But when the body goes down still eclipsed — ગ્રસ્તાસ્ત, grastasta — the ordinary observer must wait for it to come back up clear: the next moonrise for a lunar eclipse, the next sunrise for a solar one. That can be a further half-day of fasting.

A child, an elderly person or someone unwell does not wait. Their restriction ends when the eclipsed body sets, because at that moment the darshan is over. The same visibility principle that governs section 7 governs the release: no Rahu in the sky, nothing to observe.

Bolton, UK — where the concession and the ordinary rule part company.
EclipseChild stopsChild eatsEveryone else eats
28 Aug 2026 Lunar (grastasta)27th 22:4106:18 moonset20:08 next moonrise
26 Jan 2028 Solar (grastasta)12:2217:51 sunset27th 08:03 next sunrise
12 Jan 2028 Lunar (ordinary)11th 20:1504:41 — both, at moksha
On that 06:18. It is the moment the moon sets while still eclipsed. Which convention fixes “moonset” to the minute is a separate question — apparent upper limb gives 06:21:39, disc centre 06:15:37, and the Swiss Ephemeris eclipse-visibility figure the engine currently publishes is 06:18:16. A six-minute spread, and it should match whatever the moonset column of the same booklet prints.

10 What this means in practice

Use the computed local time, not the 9/12 shorthand. The saying is a fine way to remember that solar asks more than lunar, and roughly how much. It was never meant to be read off a clock against a printed eclipse table.

The engine does the full calculation for your exact location: it checks visibility first, derives your sunrise and sunset for that date, divides day and night into four watches each, finds the watch containing first contact, counts back 3 or 4, and returns the boundary — with every step of the reasoning recorded so it can be checked.