Pakistan, October 2026 and June 2028: two Rahu-return windows in 20 months.

Pakistan's national chart shows two distinct elevated windows within 20 months — October 2026 and June 2028. Both fire the Rahu-return signal at 2.51× lift. The second window adds malefic activation of the natal stellium. Pakistan's chart has historically been reactive to nodal-axis changes; the back-to-back arrival of two Rahu-return-anchored windows is unusual.

The two windows

The Rahu return — transit (Sanskrit gocara, the planet's current sky position relative to the natal chart) Rahu approaching the natal Rahu position on Pakistan's founding chart — anchors both windows. The 18.6-year nodal cycle is at its sensitive phase across both. Pakistan's chart is, in our calibration, the most node-reactive of the six national charts we track.

The signal, in plain terms

Rahu and Ketu — the lunar nodes — are the only points in the Vedic system that move retrograde and complete a full zodiac cycle on the same 18.6-year period. They mark eclipse points. The tradition reads them as the channels through which foundational themes return to the surface.

A Rahu return on a national chart — transit Rahu reaching the position it occupied at the chart's founding — is an unusually rare configuration. It happens once every 18–19 years. The activation period (the years on either side of exact return) tends to bring foundational themes back into national focus.

Pakistan's natal Rahu sits in a sensitive position. The chart shows clusters of natal placements that historically activate during Rahu-return windows. Two distinct configurations fire in our 2026–2030 scan: one approaching Rahu return, the second adding malefic-opposition pressure to the natal stellium (the term used in modern astronomical and astrological writing for a tight cluster of three or more planets in one sign) roughly 20 months later.

The math

Lift ratios

Both windows fire the rahu_return signal at 2.51× lift on Pakistan's chart. This is the third-strongest single-signal lift across the geopolitics tier of the Tempora library, behind Russia's mars_rahu (5.46×) and rahu_return (3.01×) — same-family signal, sharper on Russia.

Window 1 (Oct 2026) adds rahu_over_stellium as a secondary; Window 2 (Jun 2028) adds malefic_opp_stellium as a secondary. Both secondaries fire at lower lift but reinforce the primary signal. Window 2's combination — Rahu return PLUS malefic opposition to natal stellium — is empirically the rarer pairing.

Backtest precedent

Note #006 references Pakistan's pattern as "historically reactive to nodal axis changes" without enumerating specific named historical events. The Pakistan calibration sample is moderate (between China's N=4 and the larger India / Russia / US calibrations). Readers should weight the call as Moderate confidence — the signal is empirically real, the named precedent base is narrower than the Russia or India cases.

The atomic claims

Pakistan calibrated lift ratios — in context

The 18.6-year nodal cycle on Pakistan's chart

The forward call — both windows

We expect — and publicly commit to scoring — that Pakistan registers an elevated political or economic disruption window in both October 2026 (Window 1) and June 2028 (Window 2). For each window:

• An event of national consequence (visible across Pakistani media within days; not regional or partisan-only)
• Falls into at least one of: government collapse or formation crisis, IMF program rupture or major economic intervention, civil-military intervention into civilian government, constitutional or legal crisis at supreme-court level, or major security event with cross-border consequence
• The events in the two windows need not be of the same kind — the framework predicts elevated probability of national-consequence events, not their specific form

Falsifier — what would prove this wrong

1. Both windows pass quietly — no qualifying event within ±90 days of either Oct 15, 2026 or Jun 15, 2028 — significantly weakens the calibration of the rahu_return signal on Pakistan's chart.
2. Only one window fires — partial confirmation; the framework reads the two windows as different signal stacks, so missing one but hitting the other carries informational value but is not a clean confirmation.
3. Both fire — confirms the Pakistan-chart's nodal-axis reactivity; strongest version of the call.

What to watch — the calendars

Frequently asked questions

Read next

• Taiwan Strait risk windows: 2026-2030 forecast
• India's national chart: the 1947 chart and current dasha
• How to read a country's birth chart: the methodology
• Russia-Ukraine national charts: the peace window read
• China September 2028 forecast: Saturn approaches Moon

Disclaimer This research is published for informational and educational purposes only. Temporal pattern analysis is not a guarantee of future political, economic, security, or constitutional outcomes. Planetary cycle correlations are statistical observations derived from historical data — they describe tendencies, not certainties. No commercial, political, financial, security, or personal action should be taken based solely on the contents of this article. Tempora Research holds no political affiliation and makes no endorsement of any state, government, party, or outcome. The probabilistic ranges presented are model outputs calibrated against a limited historical event set per national chart; the Pakistan calibration carries a moderate (not large) named-precedent base. Past patterns are not guaranteed to repeat. Event dates and historical occurrences cited are from publicly available sources.

Dasha-math correction — Window 2 Mars mahadasha was Moon mahadasha (still running)

This section is a methodology revision, not a result update. Neither window's evaluation date has arrived; nothing in either call has been falsified by outcome. What has happened is a Tier 1 forward-call audit, run 5 May 2026 in the wake of the article 052 Bengal post-mortem, which compared every live forward call's cited dasha state against the Tempora canonical computation stack. The audit found that the dasha state cited in Section 1 of this article for Window 2 (June 2028) does not match the canonical computation — and, separately, that the Window 1 (October 2026) dasha state does match the canonical computation. This Section 2 documents the Window 2 divergence, re-derives what the Window 2 call rests on under the corrected reading, confirms Window 1 as verified, and states what changes — and what does not.

The audit context

The article 052 Bengal 2026 post-mortem (published 5 May 2026, within 24 hours of the counting-day result) named two specific errors that produced the failed call. The first was wrong dasha computation for both principals: Mamata Banerjee's Saturn mahadasha had ended fourteen months before the vote, and Modi was in Rahu mahadasha rather than Mars. The dasha math was not a methodology dispute; it was a calculation that did not reach the actual mahadasha boundary against the canonical natal data computed through Swiss Ephemeris with the PVRN Rao True Pushya Paksha ayanamsha. The Bengal failure prompted a corpus-wide audit of every live forward call against the same canonical stack.

That audit (workings file: Tempora's audit ledger (5 May 2026)) flagged four Tempora articles in the same family of error — articles 055, 056, 057, and this article 058 — where the article's cited dasha state diverges from the canonical computation. This article (058) is the fourth Bengal-cascade reconciliation in the corpus, after article 056 (UK), article 057 (China), and article 055 (US partial cascade). Article 058 sits structurally closest to article 055: in both cases the cascade is partial. In 055 the mahadasha was correct and the antardasha within it was wrong. In this article (058) the cascade is partial in a different way — Window 1's dasha state is fully verified against canonical computation, while Window 2's dasha state is wrong at the mahadasha layer. The Window 2 error reaches all the way to the top of the dasha stack. The Bengal failure mode reappears: Bengal had Mamata's Saturn mahadasha ending fourteen months before the vote; Pakistan W2 has Mars mahadasha not yet beginning until roughly three years after the target window.

The divergence

The chart, the ayanamsha, the house system, and the Window 1 dasha state at both layers all match the canonical computation. The divergence is in Window 2 only — at the mahadasha layer (and consequently the antardasha within it). Section 1's atomic claim — "Active dashas: W1 Moon–Saturn; W2 Mars–Venus" — survives the Window 1 half intact and does not survive the Window 2 half. Pakistan is still in Moon mahadasha at the June 2028 target window; it will not enter Mars mahadasha until 17 August 2031. The Window 2 framing is wrong by approximately three years on the mahadasha boundary.

What collapses, what stands

The article's load-bearing claims separate cleanly across the two windows. Window 1 is structurally clean. Window 2's transit-geometry argument is independent of the dasha state and survives intact; the dasha-context overlay that paired Mars mahadasha with Venus antardasha does not survive.

Window 1 — nothing collapses. The Moon mahadasha and Saturn antardasha cited in Section 1 for the October 2026 target window are both verified against canonical computation. The Rahu-return transit signal (lift 2.51×) and the Rahu-over-stellium secondary signal stand on the canonical Pakistan 1947 chart. The published call window (1 July 2026 to 31 January 2027) and the falsifier conditions for Window 1 carry through unchanged. The Window 1 dasha-context overlay — Moon-MD-with-Saturn-AD — is intact. Window 1 is structurally clean and unaffected by this revision.

Window 2 — collapses: the "Mars mahadasha with Venus antardasha" framing. Section 1's dasha-context for the June 2028 target window — "Active dasha: Mars mahadasha · Venus antardasha" — does not survive contact with the canonical computation. Pakistan is in Moon mahadasha through 17 August 2031; the Mars mahadasha cited for Window 2 has not yet begun. Any reading that depended on Mars's life-period theme contextualising the June 2028 window — Mars's lordship of houses on the Pakistan 1947 lagna, Mars-as-warlord-period overlay, or any Mars–Venus pairing's specific energetic colouration — is structurally inapplicable. The Window 2 dasha-context overlay is retired in full. The atomic-claim block's Window 2 phrasing is retired.

Window 2 — stands: the Rahu-return transit signal. The Rahu-return transit signal (lift 2.51×) on the canonical Pakistan 1947 chart is positional fact. Transit Rahu approaches the natal Rahu position on Pakistan's founding chart on the same dates regardless of which Vimshottari sub-period is running on Pakistan's chart. The 18.6-year nodal cycle's geometry at the June 2028 target window is unchanged by the dasha correction. The published Window 2 call window (1 March 2028 to 30 September 2028), the orb-based timing (window opens, peak, window closes), and the falsifier conditions for Window 2 all carry through.

Window 2 — stands: the malefic-opposition-stellium secondary signal. The malefic_opp_stellium signature firing on the natal Pakistan 1947 stellium in the same window is also a transit-geometry configuration, computable from any sidereal stack against the canonical natal data. It is unchanged by the antardasha correction. The Window 2's distinctive feature — the rarer pairing of Rahu return PLUS malefic opposition to natal stellium — is preserved.

Window 2 — carries a calibration-revision note: the 2.51× lift figure. The 2.51× lift on the rahu_return signal was calibrated on transit-geometry, not on dasha state. As a transit-only number it is intact and applies to both windows on the same chart. The flag, matching the handling adopted in articles 055/056/057: if the dasha states at the calibration's underlying historical events were also computed against a non-canonical Pakistan chart or by manual estimate — the same failure mode that produced the wrong Window 2 mahadasha — then any implicit dasha-overlay component of the calibration's interpretation may have leaned on a wrong-dasha context. The 2.51× figure is preserved as published; the dasha-overlay component of the calibration carries a recomputation flag.

What Moon mahadasha with Mercury antardasha activates on Pakistan 1947

The structural reason this matters is that Moon and Mercury rule different houses — and signify different domains — than Mars and Venus do, on any chart, for any given lagna. An antardasha is a sub-period activation of the houses ruled or occupied by the sub-lord, layered on top of the houses activated by the mahadasha lord. Mars mahadasha with Venus antardasha would have activated, on the canonical Pakistan 1947 lagna, Mars's positional placement and the houses Mars rules (the two signs Mars owns under the lagna in question), within a Mars-themed life period — read conventionally as a war-and-conflict period overlaid with a Venus sub-lord that conventionally moderates or contradicts the Mars colouration depending on functional lordship. Moon mahadasha with Mercury antardasha activates the houses Moon rules from the canonical Pakistan 1947 lagna (a single sign — Cancer — wherever it falls), and the houses Mercury rules (the two signs Mercury owns), within a Moon-themed life-context — read conventionally as a public-mood, electorate, masses, water, agriculture, perception-and-narrative period, overlaid with a Mercury sub-lord that brings communication, commerce, intermediation, and negotiation themes.

Conventionally, Moon mahadasha with Mercury antardasha is a benefic-on-benefic period — both natural benefics, with Mercury further enhanced by being natally close to Moon in many configurations — which the tradition reads as a generally favourable backdrop with the specific colouration depending on each planet's functional lordship and placement on the chart in question. This is a structurally different signature from the Mars-MD-with-Venus-AD "war-period-with-pleasure-overlay" reading Section 1 implicitly leaned on for Window 2. Whether the Moon–Mercury sub-period reads as smoothly benefic on the Pakistan 1947 chart specifically — or whether Mercury's functional lordship under the canonical Pakistan 1947 lagna pulls it into a more pressured reading (Mercury can be a maraka, a separative significator, or a 6/8/12 lord depending on the lagna) — depends on Mercury's house lordship and placement under the canonical 09:00 PKT Karachi chart, which has not been computed and recorded as part of this Section 2.

The full functional-lordship analysis of Mercury under the canonical Pakistan 1947 lagna is owed as a follow-up workings file, matching the handling adopted in articles 055, 056, and 057. The interim point is the one Section 1 made implicitly and which the audit makes explicit: dasha state — at every level cited — is load-bearing for any reading that claims a planet's sub-period theme contextualises a planet's transit signal. The two need to be the correctly-computed planet for the contextualisation to apply. Rahu-return-during-Mars-MD-Venus-AD is one configuration. Rahu-return-during-Moon-MD-Mercury-AD is a different configuration with a different background reading. The same applies to the Window 2 malefic-opposition-stellium signal.

What this means for the forward call

Both windows stay live in the tracker. Window 1 is fully clean — the call's transit signals stand, the call's dasha-context stands, no piece of the Section 1 framing for October 2026 requires revision. Window 2's chart-geometry signals — Rahu return at 2.51× lift and the malefic-opposition-stellium secondary — fire positionally and are unchanged by the dasha correction; the Window 2 falsifier conditions, window dates, and orb-based timing are unchanged. The recommendation to score both windows for elevated political or economic disruption events of national consequence carries through.

What changes is the Window 2 dasha-context overlay. The article will no longer be defended on the basis that a Mars mahadasha (with Venus antardasha) contextualises the June 2028 transit signature. The defence is narrower at the Window 2 dasha layer: Window 2's transit-based component — the Rahu return at 2.51× lift, plus the malefic-opposition-stellium secondary, both computed positionally on the canonical Pakistan 1947 chart — is the load-bearing argument. The canonical Moon mahadasha with Mercury antardasha provides the corrected dasha-context, with full Moon-MD/Mercury-AD functional-lordship analysis owed as a follow-up workings file. The Mars-MD-with-Venus-AD framing is retired. If Window 2 hits at evaluation date, it hits as a transit-geometry call within a correctly-named Moon mahadasha rather than as a Mars-MD-stacked call. If it misses, the miss is informative for the rahu-return transit signature on Pakistan 1947 independently of the (now-corrected) dasha context. Window 1's evaluation is unaffected by this revision in any direction.

The corpus context — Bengal cascade

The Bengal 2026 failure (article 052) named manual-dasha-computation-without-canonical-stack-verification as one of the two errors that produced the wrong call. The Tier 1 audit confirmed this is a corpus-level pattern. It appears in articles 052 (Bengal — both Mamata's Saturn MD and Modi's Mars MD wrong), 056 (UK — Saturn MD claimed, canonical Mercury MD), 057 (China — Rahu MD claimed, canonical Mercury MD), 055 (US — MD correct, AD wrong: Rahu AD against canonical Jupiter AD; partial cascade), and this article 058 (Pakistan — Window 1 verified, Window 2 MD wrong by approximately three years; partial cascade in a different shape). All five use the same Note #006 methodology and were drafted in the same batch (3 May 2026), before the canonical-stack discipline was formalised post-Bengal in Tempora's canonical chart methodology on 5 May 2026.

The error is consistent across the five cases: manual dasha estimation diverges from canonical computation. The depth and shape of the divergence varies — 052, 056, and 057 have wrong mahadashas at every cited window; 055 has a correct mahadasha with a wrong antardasha within it; this article 058 has one window fully correct and a second window wrong at the mahadasha layer (off by approximately three years). The fix is the same regardless of depth or shape: declare the canonical chart in Tempora's canonical chart methodology, compute the Vimshottari ladder via engine/dasha.py against the canonical natal data, and check the cited dasha state at every cited window against that computation before the analysis goes to publication. No manual estimates.

This article's Section 2 is the fourth of four Section 2 methodology revisions resulting from the audit, alongside articles 056 (UK), 057 (China), and 055 (US). Each documents its specific divergence, re-derives the call's load-bearing components, and states what stands and what retires. The work is computation hygiene, not analytical disagreement — the fix is "compute against the canonical stack before publishing the analysis," and the discipline applies retrospectively to the live calls drafted before the discipline was formalised.

Recommendation

References (Section 2)

• Tier 1 forward-call audit verdict — Tempora's audit ledger (5 May 2026) (5 May 2026)
• Article 052 Bengal post-mortem — Section 2 of article 052 (the failure that prompted the audit)
• Article 055 US Section 2 — US Jupiter-antardasha reconciliation (sibling correction in the same audit batch — closest analogue: also a partial cascade)
• Article 056 UK Section 2 — UK Mercury-mahadasha reconciliation (sibling correction in the same audit batch)
• Article 057 China Section 2 — China Mercury-mahadasha reconciliation (sibling correction in the same audit batch)
• Canonical-charts decision-of-record — Tempora's canonical chart methodology (5 May 2026)
• Pakistan 1947 canonical natal — tools/natals/pakistan_1947.json

Engine canon antardasha at both windows + Note 005 calibration depletion

On 9 May 2026 Tempora's internal audit (run via engine/dasha.py and engine/ephemeris.py) caught two further errors that Section 2 (5 May 2026) did not surface, plus an inherited Note 005 reconciliation that flags the Pakistan rahu_return calibration as the most-depleted of the corpus. The article is reconciled below per the discipline that catches errors should be published, not silently edited.

Error 1. The Window 1 antardasha. Saturn AD attribution wrong against engine canon

The 5 May Section 2 above accepted the Section 1 attribution of Window 1 (15 October 2026) as Moon mahadasha with Saturn antardasha. The 9 May 2026 audit re-ran engine/dasha.py against the canonical Pakistan 1947 natal data (14 August 1947, 09:00 PKT Karachi at 24.8607 degrees N, 67.0011 degrees E, Swiss Ephemeris with True Pushya Paksha PVRN Rao ayanamsha) and the engine returns the following dasha state at 15 October 2026.

Moon mahadasha 18 May 2025 to 18 May 2035 (10-year period). Mars antardasha 18 March 2026 to 17 October 2026 (within Moon MD, 7-month sub-period). Rahu antardasha 17 October 2026 to 16 April 2028 (within Moon MD, 18-month sub-period). The natal Moon under engine compute sits at sidereal longitude 86.03 degrees (Gemini 26.03 degrees), in Punarvasu nakshatra pada 2 (ruler Jupiter).

The Window 1 peak (15 October 2026) sits two days before the boundary into Rahu antardasha. The window itself (1 July 2026 to 31 January 2027) spans Mars AD (most of the first half) then Rahu AD (17 October 2026 onward). The Saturn antardasha attribution in both Section 1 and the 5 May Section 2 is wrong; Saturn antardasha within Moon MD does not run until 16 April 2028 to 15 November 2029, two years after Window 1 closes. Mars AD activates themes of action, conflict, military and security forces; the transition into Rahu AD adds nodal-amplification and foreign-exposure themes from 17 October 2026.

Error 2. The Window 2 antardasha. Mercury AD attribution wrong against engine canon

The 5 May Section 2 corrected Section 1's Mars MD framing for Window 2 to Moon MD and attributed the antardasha as Mercury. The 9 May 2026 audit returns engine canon at 15 June 2028 as Moon mahadasha with Jupiter antardasha (2028-04-16 to 2029-08-15) and Jupiter pratyantardasha (2028-04-16 to 2028-06-19). Mercury antardasha within Moon MD does not run until 15 November 2029 to 16 May 2031.

The Window 2 peak (15 June 2028) sits four days before the Jupiter PD boundary (19 June 2028). The window itself (1 March 2028 to 30 September 2028) spans Rahu AD (opening edge) then Jupiter AD (16 April 2028 onward, dominant through the window). Jupiter AD activates themes of expansion, sanction, foreign relations, judiciary and treaties. The Section 2 implicit "Mercury AD as benefic-on-benefic with Moon MD" reading shifts to "Jupiter AD as benefic-on-benefic with Moon MD," a different functional flavour. Functional-lordship analysis under the canonical Pakistan 1947 Virgo lagna is owed as a follow-up workings file.

Note 005 calibration depletion: the rahu_return signature

The parallel Note 005 reconciliation (commit 67f6396 on 9 May 2026, branch pending-review/notes-reconciliation) re-verified the calibration's named historical events against engine geometry under the canonical chart stack. For the Pakistan rahu_return signature with 8-degree orb, four named precedent events were checked: the December 1971 Bangladesh secession, the December 1979 Soviet invasion of Afghanistan (Pakistan-impact), the October 1999 Musharraf coup, and the April 2022 Imran Khan parliamentary dismissal. Only the 2022 event passes the 8-degree orb test against the canonical Pakistan 1947 chart at 09:00 PKT Karachi. The other three events do not show transit Rahu within 8 degrees of natal Rahu at the relevant dates.

The implication. The 2.51x calibrated lift figure for rahu_return now rests on N=1 verified historical precedent rather than the implicit N=4 Section 1 and the 5 May Section 2 leaned on. The figure is preserved with a calibration-depletion footnote: any future Pakistan forward call citing rahu_return at 2.51x must disclose this depletion. This is the most-depleted single-signature calibration in the corpus by named-event count.

The forward-call disposition

Both forward calls (W1: a Pakistan elevated political or economic disruption event of national consequence between 1 July 2026 and 31 January 2027; W2: same between 1 March 2028 and 30 September 2028) stay live in the tracker. The window dates and the falsifier conditions in Section 1 are unchanged. The reconciliation commitment to publish a post-mortem within 30 days of each window's close is unchanged.

What changes is the dasha-context overlay. The engine canon is W1 Moon MD with Mars AD (boundary case 2 days from Rahu AD start) and W2 Moon MD with Jupiter AD and Jupiter PD. The Note 005 calibration-depletion footnote attaches to the 2.51x rahu_return lift figure across both windows. The transit-geometry signals (rahu_return primary plus rahu_over_stellium secondary at W1, malefic_opp_stellium secondary at W2) all stand on engine canon as positional facts.

What stands and what retires after 9 May 2026

Stands. Both forward-call windows (W1 1 July 2026 to 31 January 2027, peak 15 October 2026; W2 1 March 2028 to 30 September 2028, peak 15 June 2028). The three falsifier outcomes scored across both windows. The reconciliation commitment to publish within 30 days of each window's close. The Pakistan 1947 chart at 14 August 1947, 09:00 PKT Karachi as the canonical natal (Virgo lagna per Note 009 reconciliation, NOT 00:00 PKT Taurus lagna as some pre-canonical drafts had used). The Moon mahadasha context (engine confirms Section 2's 5 May correction). The transit-geometry signals at both windows.

Retires. The W1 Saturn antardasha attribution (engine returns Mars AD with Rahu AD beginning 2 days after the peak). The W2 Mercury antardasha attribution (engine returns Jupiter AD with Jupiter PD at the peak). The implicit framing that the 2.51x rahu_return lift carries the same calibration weight as the other primary signatures in the corpus (Note 005 reconciliation surfaces 1-of-4 named-event verification, the most-depleted calibration in the corpus).

Owed. Functional-lordship analysis of Mars (W1 AD), Jupiter (W2 AD and PD) under the canonical Pakistan 1947 Virgo lagna. Reconstruction of the Pakistan rahu_return calibration from a wider precedent base, or explicit acceptance that the calibration rests on N=1 verified precedent. Engine sweep of any other calibrated Tempora signature firing on the Pakistan 1947 chart at either window.

References (Section 3)

• 9 May 2026 audit ledger: internal audit log maintained (run via engine/dasha.py and engine/ephemeris.py)
• Pakistan 1947 canonical natal: tools/natals/pakistan_1947.json (14 August 1947, 09:00 PKT, Karachi 24.8607 degrees N, 67.0011 degrees E, Virgo lagna per Note 009 reconciliation)
• Sibling 9 May 2026 reconciliations: Note 005 calibration reconciliation (commit 67f6396, surfaces Pakistan rahu_return depletion to 1-of-4 verified events), Note 006 register card Pakistan dual windows (commit 4844d44), Note 009 Subcontinent Triangle Pakistan natal time canon (commit 76d782c, 00:00 to 09:00 PKT correction)
• Sibling article reconciliations: article 055 US Section 3 supersession (this batch, prior commit), article 056 UK Section 3 supersession (this batch, prior commit), article 057 China Section 3 supersession (commit 1e239cd), article 044 Russia-Ukraine Section 3 supersession (commit 07725b5), article 029 India national chart Rahu-MD retirement (commit 6ea1d5d)
• Standards reconciliation: docs/principles/research_publishing_standards.md failure modes 10.6 (self-contradicting Section 2) and 10.8 (Section 1 banner discipline)
• Cascade audit: docs/audit/2026_05_09_cascade.md (commit c59b946) and docs/audit/2026_05_09_research_notes_audit.md (commit 5c3e739)