Our method
Show the working.
A precise time is useful only when you can see what it measures. Here is how this first collection was assembled and what it cannot tell you.
One instant, then local clocks
The primary Moon phase times in this preview come from the U.S. Naval Observatory’s 2026 table. We record each instant in UTC. For the featured October new and full moons, we compared the minute with NASA GSFC’s archived Sky Events Calendar; its times agree. The remaining list follows the Observatory table. Source records were checked on 2026-09-29.
A browser then converts the UTC instant to the time zone you select. We use named IANA zones so the offset comes from the event date, including daylight-saving rules. Without JavaScript, UTC remains visible. The selected location changes the label on the clock, never the moment itself.
NASA’s archived calendar asks for acknowledgment when its data are reproduced: Sky Events Calendar by Fred Espenak and Sumit Dutta (NASA’s GSFC). We use it here as a comparison source, not as a claim that two institutions used wholly independent underlying calculations.
Three different kinds of statement
Calculated fact
A phase instant and its UTC-to-local conversion. The method and source can be inspected.
Traditional reading
What a named astrological school makes of a configuration. That requires its own rules and editorial review.
Your reflection
A question to help you notice what matters to you. It is not a discovered fact about your life.
A local horizon, then daily divisions
The daily timing calculator uses Astronomy Engine 2.1.19 to find sunrise and sunset at approximate city-centre coordinates. Its astronomical convention uses the Sun’s upper edge, standard atmospheric refraction and a clear horizon at zero elevation. Unlike a global Moon phase, these instants change with the place.
Rahu Kalam, Choghadiya and Hora then divide the daylight and night according to weekday rules. Their traditional names are not predictions. The calculator shows its inputs and limits; the traditional rules still need specialist review. Solar fixtures were compared with the U.S. Naval Observatory for Bengaluru and the 2026 London and Sydney daylight-saving change dates.
Moonrise and additional daily periods
Moonrise and moonset use Astronomy Engine’s topocentric upper-limb rise/set search, with the same observer, standard refraction and zero-elevation convention. We search the selected local civil date, including its daylight-saving length; “no event” means no rise or set was found in that date window. Night duration is elapsed time from sunset to next sunrise.
Daytime Gulika and Yamaganda each select one of eight daylight divisions by weekday. Brahma Muhurat here follows the fixed convention shown by Muhuratam: 96 to 48 minutes before sunrise. It is not a seasonally scaled night-muhurta calculation. Abhijit uses the eighth of fifteen daylight divisions and is omitted on Wednesday, following Drik’s stated convention. These references are separate intervals; we do not subtract all conflicting rules or present them as complete event recommendations. Specialist rule review is pending.
The current moment and the next window
The home-page “Now & next” desk uses the current instant, rather than the noon reference used for the three daily themes. Moon illumination and the next exact primary phase are calculated with Astronomy Engine 2.1.19. The schematic terminator uses the calculated lit fraction; surface textures and hemisphere orientation remain illustrations, without local tilt or libration. Each build prepares individual downloads for the next 56 primary phases. The browser links only to files in that build’s manifest; beyond it, the browser can generate a file locally. Calendar files contain the global phase instant in UTC and no birth information. The 13 retained October–December 2026 USNO phase references are checked within a 90-second threshold; this does not validate the entire future archive. A static page labels its build snapshot; live browser answers update at timing changes, at least once a minute, and when the page returns to view.
Current and next Choghadiya and Hora use the previous, current and following solar cycles. Before sunrise, the active night belongs to the previous sunrise day. Each interval includes its start and excludes its end. Upcoming horizon events search 48 elapsed hours from the current instant, including overnight and daylight-saving changes; if a rise or set is absent in that span, the desk says so. Current Tithi and Nakshatra use the instant directly and show their next boundaries. They do not assign a festival or ritual day.
A “checked window” is the remaining part of an Amrita, Shubha or Labha Choghadiya after subtracting any overlapping Rahu Kalam, Yamaganda and daytime Gulika periods. The subtraction handles partial and overlapping exclusions. It does not include night Gulika, Var Vela, Kaal Vela, Kaal Ratri, birth-chart compatibility or event-specific rules; it is not a complete muhurat recommendation. The active exclusion and overlaps with the current slot are shown separately. Profile: now-next-1.0; specialist rule review remains pending.
How we choose today’s three feelings
The landing page is a collective Western tropical astrology reading. It offers three themes for reflection, not a measurement of public mood or a personal prediction. The planetary positions are calculated; their emotional associations are original editorial interpretations. We do not claim that a majority of people will feel these things or that planetary geometry establishes a cause for a person’s mood.
Each reading uses local noon on the current civil date in the selected time zone. Sun and Moon longitudes use the same functions as the birth calculator; the other planets use apparent geocentric vectors converted to the true ecliptic of date. The positions table gives the reference instant. Different clocks can select different reference instants; geography does not change geocentric positions at the same instant.
The first theme follows the Moon’s tropical sign. The other two use distinct close major aspects involving the Sun, Moon, Mercury, Venus or Mars: conjunction, sextile, square, trine and opposition. The selection allows three degrees from exact for Moon aspects and two degrees for other aspects, gives Moon aspects priority, then favours closer relationships. These are our editorial selection conventions, not probabilities. Slow-planet pairs alone are excluded from the daily selection. When there are too few distinct aspect themes, explicitly named sign-based themes fill the remaining slots.
The browser refreshes at local midnight and when a returning tab becomes visible. On Cloudflare Pages, a prepared home-page Function also puts a fresh UTC reading in initial HTML; that Function has not been deployed. A purely static preview has a dated build snapshot without JavaScript. These rules and original reflection prompts use version daily-tropical-1.0; specialist interpretation review is pending. Background references: Astrodienst’s aspect introduction and its discussion of planetary symbolism.
A personal reading for the next seven days
The hero’s single private form now calculates all ten planet positions and the Rising point from a recorded birth time. Its seven-day reading compares transiting planets with natal Sun, Moon, Mercury, Venus, Mars and Rising. It uses the same five major aspects as the collective reading, allowing three degrees for the transiting Moon and two for other planets. Moon contacts take priority, then personal-planet contacts, then slower planets; closer contacts break ties. Only one selected theme is shown per day. This is a limited transit reading, not a complete natal interpretation.
Each date uses noon in the visitor’s chosen current time zone. The visible basis names the transiting planet, aspect, natal point and distance from exact. Noon sampling can miss a Moon contact that occurs at another hour; this feature does not promise an exact event time. Slower contacts may repeat across several dates and are labelled as a continuing period. If no contact qualifies, the page explicitly falls back to a general Moon-sign reflection. It never invents a personal aspect to fill the day.
Unknown birth time retains the possible Sun and Moon placements but does not produce exact natal transits or Rising. Results stay in page memory, refresh after time-zone changes and at local midnight, and clear with the inputs. Interpretations are original editorial work with specialist review pending. Version: personal-tropical-1.0.
Daily and monthly Panchang
Daily Panchang and the monthly view share profile lahiri-ae-1.0. Sun and Moon geocentric longitudes come from Astronomy Engine 2.1.19. The sidereal offset is independently implemented by rotating a fixed J2000 ecliptic origin to the true ecliptic of date. Its mean Lahiri anchor is 23°51′25.5324″ at J2000 TT, taken from Swiss Ephemeris documentation, Appendix E. The rotation uses Astronomy Engine’s precession and nutation. This is a Lahiri anchored implementation, not the Swiss Ephemeris library or a claim that every Lahiri variant is identical.
Tithi divides normalized Sun–Moon separation into 30 parts of 12 degrees; karana divides it into 60 parts of six degrees, with the seven repeating and four fixed names. Nakshatra uses 27 equal sidereal Moon sectors and pada their 108 subdivisions. Yoga divides the normalized sum of sidereal Sun and Moon longitude into 27 parts. Boundary searches retain subsecond numerical brackets. This search resolution is not an astronomical accuracy claim.
The selected day begins at the calculated local sunrise and ends at the next sunrise. It uses the upper-limb, standard-refraction, zero-elevation horizon convention described above; different ritual sunrise conventions can change which limb belongs to a sunrise very close to a transition. No complete sunrise cycle means the page instead labels a local-midnight reference, leaves Vara unavailable and does not assign a ritual day. Overnight dates are explicit. Times are rounded to the nearest minute for display.
Amanta month names come from the sidereal solar sign at the enclosing new-moon boundary. A lunation with no solar ingress is marked Adhika. Regular waning fortnights use the following lunar month name in Purnimanta; an Adhika lunation remains a whole new-moon cycle in both conventions. Rare two-ingress month sequences withhold a month name pending review. The default is explicitly Amanta, with a Purnimanta selector; geography does not decide someone’s tradition. The monthly view uses the same daily calculation and marks tithis that repeat at sunrise or pass between sunrises. It does not assign festivals or fasting dates from a single sunrise label.
References checked through 2 October 2026 include six published mean Lahiri values across 1950–2020 and twenty-six minute-rounded limb/pada end times from Drik’s Bengaluru day page and its 1 June and 2 October, 21 June and 21 December 2026 Washington pages. Washington end times are converted to UTC and checked in a New York sunrise window; the limb boundary is global, while window membership is local. The acceptance thresholds are one arcsecond for those ayanamsha examples and 90 seconds for those end times. These selected fixtures do not validate every supported date, festival rule, region, month exception or historic time zone.
Choose a place, see its source
City search uses 34,125 populated-place records across 244 countries and territories, derived from the GeoNames cities15000 export retrieved on 2 October 2026. Names, WGS84 coordinates and named time zones come from that export; country and region labels come from GeoNames countryInfo and admin1CodesASCII. The source archive checksum and transformation record are available here. Ten earlier quick presets keep their existing coordinates and stable share links.
GeoNames data are used under Creative Commons Attribution 4.0; we split the export into country files, retain up to 24 alternate names and omit historical, abandoned, destroyed or invalid-coordinate records. Search accepts accented names and ASCII spellings. Region labels distinguish cities sharing a name. A result must be chosen explicitly; typed text alone does not set a calculation location. The catalogue covers many cities and towns, not every village, address or historical birthplace. Manual birth coordinates remain available.
Country files are fetched from this site on demand for selected, saved or shared-link locations. Search text and birth details are not sent to a search provider. Coordinates represent a place centre, not a hospital or surveyed horizon. Zero elevation remains the calculation convention. The named zone uses the browser’s date-specific time-zone rules; source labels do not prove every historical clock rule. Country selection does not choose a religious tradition or change a regional edition.
Sun, Moon and Rising from birth details
The home-page calculator leads with three placements in the Western tropical zodiac, using equal 30-degree signs from the equinox. “Find my signs” shows Sun, Moon and Rising first; a known-time result can then open the seven-day reading and its other calculated planets without asking for the same details again. The sign guide carries those placements within the current page, labels possible signs when the birth time is unknown, and clears them when the inputs change. Astronomy Engine 2.1.19 supplies the Sun’s apparent geocentric ecliptic longitude and the Moon’s geocentric ecliptic longitude of date. The Rising point is the eastern intersection of the ecliptic and geometric horizon at the entered time and coordinates; atmospheric refraction is not applied to this point. This is not a sidereal or Vedic birth calculation.
Birthplace and current location are separate inputs. Presets use approximate city centres; a custom birthplace needs coordinates and an IANA time-zone name. Browser time-zone rules convert the recorded civil time to UTC. A skipped clock time is rejected, and a repeated clock time requires choosing its occurrence. Historical clock rules depend on the browser’s time-zone database and may need checking against the birth record.
With no birth time, we check the Sun and Moon over the entire local civil date, show both signs if a change occurred, and leave Rising unknown. Results near a sign boundary are flagged for extra care. Degrees are truncated to a tenth within the calculated sign to avoid rounding into a different sign. Birth details are processed in page memory and are not saved or sent to another service.
Verification includes two UTC Sun/Moon positions from NASA/JPL Horizons and the published three-placement example for Marilyn Monroe in Astro-Databank, checked on 30 September 2026. The fixture tolerance is 0.02 degrees; it is a test threshold for these examples, not an accuracy guarantee for every birth. Tests also check the Rising point against the eastern geometric horizon and civil-time handling at daylight-saving transitions.
Moon illustrations
The calendar’s SVG diagrams follow the phase sequence explained in NASA’s Moon phase guide. Craters and surface shading are illustrative, not surveyed lunar terrain. Crescent and gibbous diagrams use representative intermediate shapes; they do not add new dated events. A hemisphere control rotates the schematic view, but actual tilt and libration depend on the observing place and time. Illustration orientation never changes a phase instant.
What is not here yet
The personal transit reading is not a complete natal chart: house systems, a natal aspect wheel, Vedic birth-chart conventions and a complete interpretation still need implementation and review. This preview does not predict a personal outcome. Complete event muhurat, festival/fasting-day assignments, regional exceptions and smaller or historical birthplace coverage remain work. Interpretive copy and traditional rules require specialist review before publication.
The October first-quarter value is 16:12 UTC in the Observatory table and 16:13 in NASA’s archived calendar. We follow the Observatory for the list and do not draw an interpretation from that one-minute difference. Any deeper explanation of the discrepancy should be investigated before publication.
Corrections and release status
This is an editorial preview. The proposed correction address is contact@thetimingchart.com; its delivery must be tested before launch. A named publisher, author credits, and specialist review are still needed before public indexing. If a time is found to be wrong, the affected page and calendar file must be corrected together, with a dated note explaining the change.