July 2026 Panchang Calendar — Noida
Every tithi and nakshatra below is the one in force at Noida's own sunrise on that date — Gautam Buddh Nagar sits at 77.39°E, so a day can carry a different tithi here than in a calendar computed for another meridian when a boundary falls near dawn. The lunar month is labelled by the purnimanta convention this city uses.
| Measure | Value |
|---|---|
| Lunar months spanned | Shravana–Ashadha |
| Earliest sunrise | 05:26 |
| Latest sunrise | 05:42 |
| Longest day | 836 minutes |
| Shortest day | 811 minutes |
| Ekadashi days | 1 |
| Purnima / Amavasya | 1 / 1 |
| Mornings whose tithi differs from New Delhi | 0 |
Sunrise in Noida moves from 05:26 on the 1st to 05:42 on the 31st, and sunset from 19:22 to 19:12 — the day shortens by 25 minutes across July, which drags every kaal window and every Choghadiya slot with it.
On none of the 31 mornings this month does the tithi at Noida's sunrise differ from the one at New Delhi's — every boundary this month happens to fall clear of both dawns.
The two times under each date are that morning's sunrise at Noida and the start of that day's Rahu Kaal, which is the eighth of real daylight assigned to Rahu on that weekday. Both move with the city, not just with the date: they are what a calendar computed for another meridian gets wrong even on the days it agrees about the tithi.
Noida and New Delhi share one sky
Across the 365 mornings of the year, sunrise at Noida never differs from sunrise at New Delhi — 20 km away — by more than 54 seconds, and on 364 of those 365 mornings the tithi and nakshatra standing at the two sunrises were the same — they part on 1 morning of the year, when a boundary happens to fall in the seconds between the two dawns. Two calendars that agree that closely are, for indexing purposes, one calendar.
So this page is canonicalised to the New Delhi calendar: search engines are told to treat that one as the copy of record instead of indexing this as a second version of it. Nothing is removed — the page stays, because people look for Noida by name, and every figure on it is computed for Noida's own coordinates, 28.54°N 77.39°E, rather than copied across.
Observances in July 2026
| Date | Observance | Tithi it is fixed to | What the day is |
|---|---|---|---|
| 16 July | Rath Yatra | Ashadha Shukla Dvitiya | The Puri and Ahmedabad chariot processions; Bhubaneswar keeps its own rath on a different tithi in Chaitra. |
| 25 July | Devshayani Ekadashi | Ashadha Shukla Ekadashi | Chaturmas begins; the four months in which the classical texts bar most new beginnings. |
| 29 July | Guru Purnima | Ashadha Shukla Purnima | Vyasa Purnima — the teacher's full moon, and the start of the monsoon retreat. |
Why the month is named what it is here
Noida is in Uttar Pradesh and reads the month purnimanta, like the rest of the state — but it sits on the eastern side of the NCR at 77.39°E, so its sunrise arrives about forty-five seconds before Delhi's. That is smaller than the width of most tithi boundary readings, which is exactly why this page prints the boundary time rather than only the tithi name.
How a festival lands on a date
None of the dates above is stored. Each observance is held here as the rule that defines it — a lunar month, a fortnight and a tithi — and resolved against the computed panchang for Noida each time this calendar is rebuilt, which is why the same festival moves through the Gregorian year and why two adjacent cities can differ by a day. The lunar month name follows the purnimanta reckoning; the intercalary adhika masa, which repeats a month name roughly every thirty-two months, is detected and its festivals are attributed to the regular month rather than the leap one.
A day is marked by the tithi standing at sunrise. Observances that are settled at another moment — Janmashtami at midnight, Diwali at pradosh, Ahoi Ashtami at starrise — can therefore be announced by a temple one day either side of the marker here, and the table above says so where it applies. Solar festivals such as Makar Sankranti are keyed to the Sun's ingress instead, which is why they barely move.