India beat West Indies by eight wickets in the first T20I at Lucknow on Tuesday, 6 October 2026, completing a rapid chase built around Shreyas Iyer’s unbeaten century. West Indies were bowled out for 171 in 19.1 overs, but India needed only 14.4 overs to reach 172/2 and finish with 32 balls remaining. [1][2][3]
The result gives India an early lead in the five-match T20I series and provides a clear answer to the immediate question around the match: India won the 6 October game. It also needs a careful date and format label because West Indies had won a different fixture three days earlier—the third ODI in New Chandigarh. That 3 October match ended with West Indies winning by five wickets, so its result and score must not be folded into this Lucknow T20I report. [3][6][7]
Key points
- India beat West Indies by eight wickets in the first T20I in Lucknow on 6 October 2026. [1][2]
- West Indies made 171 all out in 19.1 overs; India finished on 172/2 in 14.4 overs. [2][4]
- Shreyas Iyer scored 102 not out from 43 balls, including 10 fours and six sixes. [3][4]
- Ishan Kishan remained unbeaten on 37, while Naman Dhir took 3/31 on his T20I debut. [3][4]
- This was separate from West Indies’ five-wicket win over India in the 3 October third ODI. [6][7]
What happened in Lucknow
The official BCCI scorecard identifies the match as the first T20I between India and West Indies on 6 October at the Bharat Ratna Shri Atal Bihari Vajpayee Ekana Cricket Stadium in Lucknow. Its figures match the independent reports: West Indies were dismissed for 171, and India’s 172/2 came in 14.4 overs. [1][2]
That margin tells the story of a chase that moved decisively in India’s favour. Winning with 32 deliveries still unused left no late contest over the final runs. The available reports support the verified totals, overs and named contributions, but not a reconstruction of each delivery or detailed tactical claims.
West Indies still had two substantial individual scores in their innings. Reuters reports that Shai Hope made 52 and Sherfane Rutherford scored 56, but the total did not withstand India’s bowling pressure. Naman Dhir returned 3/31, with Axar Patel taking 2/26, according to the independent match reports. [3][4]
Iyer turns the chase into a sprint
The defining performance came from Shreyas Iyer. He made 102 not out from 43 balls, with 10 fours and six sixes, as India chased down the target well inside 15 overs. Reuters and ESPNcricinfo both record the unbeaten 102, while ESPNcricinfo describes it as Iyer’s maiden T20I hundred. [3][4]
Ishan Kishan’s unbeaten 37 provided the other named contribution in the successful chase. Together, the two not-out scores explain why India lost only two wickets while converting a target of 172 into a comfortable win. The figures also give readers a more useful measure of the performance than the margin alone: Iyer supplied the innings’ headline acceleration, while Kishan stayed with him through the finish. [2][4]
This is a result-led account, not a claim that one innings settles the series. A first-match win can change the pressure around the next game, but the evidence supplied here does not establish how either side will alter its XI, batting order or bowling plans. Those questions belong to later team announcements and match evidence.
Dhir’s debut adds a second India storyline
India’s win was not only a batting story. Naman Dhir took 3/31 on his T20I debut, a contribution that helped restrict West Indies to 171 all out. Reuters, ESPNcricinfo and Olympics.com support the bowling figure, while ESPNcricinfo specifically identifies the debut. [3][4][5]
The debut detail matters because it places the result in a broader team context without overstating what can be learned from one game. Dhir made an immediate statistical impact, but the supplied sources do not establish whether he will retain his place, what role India planned for him beyond this match, or how the conditions influenced his spell. Those points should not be presented as settled conclusions.
Why the 3 October ODI must stay separate
Readers searching for India and West Indies results may encounter two opposite outcomes from the same tour. On 3 October, in the third ODI at New Chandigarh, West Indies chased 351 after India made 351/7, winning by five wickets; Shai Hope scored 162 not out. BCCI’s separate match page and ESPNcricinfo’s ODI report support those details. [6][7]
That was not the match covered here. The October 6 first T20I took place in Lucknow, a different date, venue and format. The earlier ODI’s five-wicket margin and Hope’s 162 are background to a separate game, not the score or standout innings in this one. Keeping the fixtures distinct prevents a plausible but serious scorecard mix-up.
What the result means—and what it does not
India’s eight-wicket win is a strong opening statement in the five-match T20I series because it combined a defendable West Indies total with a chase completed at high speed. Iyer’s hundred and Dhir’s three wickets give India two clear performers to carry into post-match discussion. [3][4]
But the evidence does not support broader claims about rankings, series outcome or long-term selection. It confirms one completed match and an India lead after the opener; it does not guarantee a series win or show that either side has solved its weaknesses. West Indies’ 171 included scores from Hope and Rutherford, so the next contest may turn on whether their middle-order production and resistance improve, but that is an editorial question—not a verified forecast from the opened sources.
What happens next—and what remains uncertain
The immediate next step is the next match of the five-game T20I series. The reports cited here confirm the series format but not a next-match date, venue, playing XI or injury update. Those details should be checked against a dated fixture announcement rather than guessed. Until then, the takeaway is limited and clear: India won the first T20I on 6 October in Lucknow by eight wickets.
One player-name detail also needs care. Olympics.com calls an early India batter “Abhishek Verma,” while Reuters and ESPNcricinfo identify him as Abhishek Sharma. The name is not needed to understand Iyer’s hundred or the result, and neither spelling is relied on in this match account. [3][4][5]
