Lab entry · Markets and macro · Window 15 September to 15 November 2026 · Reconciliation within 7 days of close

India festive vehicle retail 2026: the 2025 total is the bar.

The 2025 festive period ran 22 September to 2 November and rose 21 percent year on year to an all-time festive high. October 2025 retail alone grew 40.5 percent to more than 4.2 million units. Then November 2025 settled to 2.14 percent as two-wheelers fell 3.1 percent. A GST 2.0 rate cut pulled demand forward into that base, and a base built on a pull-forward is a hard base to beat. This entry takes the side that says it does not get beaten, and grades it against FADA's own festive release.

Tempora's call. FADA total vehicle retail for the 2026 42-day festive period prints at or above the 2025 festive total, that is, zero or positive year on year.

Falsifier, stated verbatim as the test table carries it: >= 0 percent YoY on FADA total festive vehicle retail fires MET. A 2026 festive total below the 2025 festive total, any negative year-on-year print, fires FAILED.

Stated probability: 0.40. Base rate: the naive always-grows base rate on Indian festive vehicle retail sits near 0.75. The stated probability sits well below it because the base period carries a one-off. GST 2.0 pulled demand forward into the 2025 festive window, October 2025 printed 40.5 percent year-on-year growth on that pull-forward, and November 2025 handed part of it back at 2.14 percent with two-wheelers down 3.1 percent. This is deliberately the contrarian side: the position is that the 2025 festive record does not hold. Calibration tier: lab, no lift claimed. Reconciliation within 7 days of the window close.

Under test in the Lab. This is an experimental signature, published on a dated window with a fixed check-back while it earns its place. It lives in the Lab, our surface for signatures still proving themselves. A call graduates to the flagship Tracker once it clears calibration. Track its window in the Lab →

What counts as the event

The qualifying observable is the total vehicle retail line in the Federation of Automobile Dealers Associations festive-period press release for 2026, all categories, compared against the same line in the 2025 release. The graded figure is a rate and not a unit bar: zero or positive year on year fires MET, negative fires FAILED. Registration-based retail is the measure, not manufacturer dispatches, because FADA's series is built from vehicle registration data and dispatches move on a different clock.

The window binds to FADA's published definition. FADA sets the 42-day festive period each year and publishes the aggregate in the same release as its October monthly data. The 2025 window ran 22 September to 2 November. The exact 2026 window binds to FADA's published 42-day festive definition for 2026 once announced, and the 15 September to 15 November 2026 dates carried on this entry are a container the published window sits inside rather than the graded period itself. If FADA's 2026 definition falls outside that container the entry is re-dated on the tracker with the reason recorded rather than being quietly regraded.

Reference for verification: the FADA festive-period press release, total retail line. The 2025 comparative comes from the FADA October 2025 and 42-days festive vehicle retail release.

The base rate, and the pull-forward that discounts it

Indian festive vehicle retail grows most years. Rising incomes, widening finance penetration and a festive calendar that concentrates discretionary purchases put the naive always-grows base rate near 0.75, and any call on the negative side has to earn its way down from there.

The base period is what earns it. The 2025 festive block did not grow at trend. It grew 21 percent year on year to an all-time festive high across the 22 September to 2 November window, and the month at its centre grew 40.5 percent to more than 4.2 million units, reported here on the FADA October 2025 data. Growth of that size in a single festive block is not a demand trend. It is a price event: GST 2.0 cut on-road prices, buyers who would have transacted across several quarters transacted inside one, and the festive window absorbed the whole of it.

The give-back showed up immediately. November 2025 retail grew 2.14 percent year on year, with two-wheelers down 3.1 percent, and FADA attributed the two-wheeler softness to the festive pull-forward. That is the shape of a pulled-forward month rather than a re-based one, and it is the single most useful number on this page: it says the 2025 festive peak borrowed from the periods around it.

So the arithmetic. To fire MET, 2026 has to match a festive block that ran roughly 21 percent above its own prior year on a one-off price cut. Flat is enough, which is why the stated probability is 0.40 rather than 0.20. But flat against a spike is a demanding ask, and the base rate built on ordinary years does not price it. Stated probability 0.40 is the naive base rate discounted hard for the one-off and then given credit for the fact that the bar is zero and not a growth rate.

Limitation, stated with the signal: a companion lab entry, FADAOCT2026, asks whether the October 2026 monthly print beats October 2025 and carries a stated probability of 0.65. This entry asks about a differently defined 42-day block and carries 0.40. The festive calendar does not sit identically inside the month each year, so the two are not the same test stated twice, but they do lean opposite ways and both cannot be well calibrated if they resolve in the same direction. That tension is recorded here rather than smoothed over, and the pair will be read together at reconciliation.

Method note, and the lesson applied

Lesson applied: state the threshold as a rate against a defined base, not as an absolute unit bar. In June Tempora published DGCAJUN2026, which required India's DGCA domestic passenger traffic for June 2026 to print above 13.5 million. The print landed at exactly 13.5 million and the call graded FAILED on the stated falsifier wording. The reconciliation recorded the real defect: June is a lean month in Indian aviation, the absolute bar took no account of that, and the underlying year-on-year comparison would have graded MET cleanly. The July entry restated the same signature as a growth rate for exactly this reason.

This entry applies the fix at the threshold. The test is a rate, zero or positive year on year, against a named base, the 2025 FADA 42-day festive total from FADA's own release. Seasonality, festive-calendar drift and category mix all sit inside the comparison rather than outside it. There is no unit number to argue about and no lean-period trap, because both sides of the ratio are the same 42-day festive block on the same series.

Limitation, stated with the fix: a rate against a defined base still inherits whatever the base did. Here the base is anomalous by design, which is the substance of the call rather than a defect in it, but it does mean a MET would be a strong result and a FAILED would be a weak one. The lab tier records that asymmetry and claims no lift.

Chart-side reading, and what it cannot do

Tempora's calibrated table carries no sector-retail signature at festive-period resolution, so nothing in this section claims a lift and nothing in it carries the call. The period state is engine-verified on 16 August 2026 against the India 1947 canonical natal chart, 15 August 1947, 00:00 IST, New Delhi, Taurus lagna. Mars mahadasha with Saturn antardasha runs across the whole window, verified at both 15 September 2026 and 15 November 2026.

That is a structural-pressure period in the classical reading, Saturn contraction operating inside a Mars major period, and it sits alongside the demand argument rather than under it. The argument that carries this call is the base: a festive block inflated by a one-off price cut, and a give-back already visible in the November print that followed it. If the call grades MET the chart-side layer gets no credit, and if it grades FAILED the demand argument gets the credit. That distinction is why the entry is in the Lab and not the Tracker.

One further constraint, declared: this entry claims no transit contact dates. The chart-side statement above is a dasha state and nothing more.

What would make this wrong

GST 2.0 was a level shift and not a pull-forward. This is the central risk. If the rate cut permanently lowered on-road prices and permanently widened the addressable buyer base, then 2026 festive volumes build on the new level rather than mean-reverting toward the old one, and the 2025 total is beaten comfortably. The November 2025 give-back argues against it. One month does not settle it.

Rural demand recovers into the festive window. Two-wheelers carry the bulk of festive units and they move on rural cash flow. A good kharif harvest, firm crop prices and easier vehicle finance would lift the largest category from the level that fell 3.1 percent in November 2025, and a two-wheeler recovery alone can carry a flat-to-positive total.

The 42-day definition moves the comparison. FADA sets the window and the festive calendar drifts against the Gregorian one year to year. A 2026 window that captures a different share of Navratri and Diwali retail than 2025 did changes what is being compared without anything changing in demand. This is the largest measurement risk on the entry and it is the reason the window binds to FADA's published definition rather than to dates Tempora picked.

Base revision. FADA restates its series as registration data settles. A downward revision to the 2025 festive total lowers the bar this call is betting against, and a MET could follow from arithmetic rather than from demand. The reconciliation will quote both totals as published on the day of grading.

A FAILED that says nothing. The failure branch has a mirror. A total that lands 1 percent below the 2025 block fires FAILED and tells a reader almost nothing about whether the pull-forward thesis was right, because a 1 percent gap is inside the noise of a shifting festive calendar. The reconciliation will report the margin so the result can be weighted honestly rather than counted as a clean hit.

How this grades

The verdict publishes within 7 days of the window close, so by 22 November 2026 on the stated container window, as a Section 2 reconciliation on this page and on the public Lab surface at the same time. The reconciliation quotes FADA's published 2026 festive window dates, the 2026 total retail figure, the 2025 comparative as FADA states it in the same release, the computed year-on-year rate, the verdict and the margin. If FADA's festive release lands after the reconciliation date the entry is re-dated as data-pending with the reason recorded, the same handling applied to DGCAJUN2026 when the DGCA release schedule moved. Losses publish on the same schedule as wins.

Frequently asked

What is the 2026 India festive vehicle retail call?

FADA total vehicle retail for the 2026 42-day festive period prints at or above the 2025 festive total, that is, zero or positive year on year. At or above fires MET. Below the 2025 total fires FAILED. Stated probability 0.40 against a naive always-grows base rate near 0.75, discounted for the one-off GST 2.0 demand pull-forward sitting inside the base period.

Which 42 days are being measured?

FADA defines the festive period each year and publishes the total in the same release as its October monthly data. The 2025 window ran 22 September to 2 November. The graded window binds to FADA's published 42-day festive definition for 2026 once announced. Until then the entry carries a 15 September to 15 November 2026 container that the published dates sit inside.

Why is the stated probability so far below the base rate?

Because the base period carries a one-off. India's GST 2.0 rate cut pulled vehicle demand forward into the 2025 festive window. October 2025 retail grew 40.5 percent year on year to more than 4.2 million units, and the 22 September to 2 November festive period surged 21 percent to an all-time festive high. November 2025 then settled to 2.14 percent as two-wheelers fell 3.1 percent on the pull-forward. Beating a base built that way is a harder ask than the always-grows base rate suggests.

What lesson from an earlier miss does this apply?

The year-on-year versus same-month discipline. The June call DGCAJUN2026 set an absolute 13.5 million passenger bar into India's lean aviation month and graded FAILED when the print landed at exactly 13.5 million, while the underlying annual growth reading held. Stating the threshold as a rate against a defined base carries the seasonal shape inside the comparison instead of leaving it in the analyst's head.

When does Tempora reconcile?

Within 7 days of the window close, so by 22 November 2026 on the stated container window, as a Section 2 reconciliation on this page and on the public Lab surface. If FADA's festive release lands after that date the reconciliation is re-dated as data-pending with the reason recorded on the tracker entry, the same handling applied to DGCAJUN2026 when the DGCA release schedule moved.