Mitchell Santner's 4/21: the first double four-wicket haul against India, but Christchurch was decided in the last thirty balls
**मुख्य उत्तर (≤60 शब्द)** मिचेल सैंटनर ने क्राइस्टचर्च में खेले गए दूसरे टी20 इंटरनेशनल में भारत के खिलाफ 4/21 लेकर पुरुष टी20 इंटरनेशनल में भारत के विरुद्ध एक से अधिक चार-विकेट हॉल लेने वाले पहले गेंदबाज़ बने। भारत ने 181 का लक्ष्य 19.5 ओवर में चार विकेट पर हासिल कर सीरीज़ 2-0 कर ली। **मुख्य तथ्य** - सैंटनर के चार ओवर में 21 रन, यानी 5.25 की इकॉनमी; चार विकेट — अभिषेक शर्मा (27), श्रेयस अय्यर (7), अक्षर पटेल (11), नमन धीर (31)। - न्यूज़ीलैंड ने पहले बैटिंग कर 180/5 बनाए; भारत 15 ओवर में 112/6 पर था, फिर 30 गेंदों में 69 रन चाहिए थे। - तिलक वर्मा 26 गेंदों पर 51 नाबाद और नितीश कुमार रेडी 13 गेंदों पर 26 नाबाद; सातवें विकेट के लिए 30 गेंदों पर 69 रन की अटूट साझेदारी। - सैंटनर का पिछला चार-विकेट हॉल भारत के खिलाफ 2016 टी20 विश्व कप के नागपुर मैच में 4/11 था, जिसमें न्यूज़ीलैंड 47 रन से जीता। - पांच मैचों की सीरीज़ में भारत 2-0 से आगे; तीसरा टी20 इंटरनेशनल अगला मुकाबला है। **स्रोत** मूल मैच रिपोर्ट: क्र
Christchurch, Saturday evening. The fifteenth over. Mitchell Santner floated one outside off stump, Naman Dhir stepped out to play the inside-out loft, the ball took the outside half and settled into Glenn Phillips's hands at extra cover. The board read 112 for 6. Santner had bowled his four overs, taken four wickets, conceded twenty-one runs: 4 for 21.
The sound that went around the ground in that moment was not the sound of a win. It was relief. The home side believed the game was in its pocket. From the dugout to the commentary box, one sentence was doing the rounds: Santner had turned the match.
I kept the chart ball by ball off the feed that evening, the old habit. Hand-ruled lines, a bowler's name under every over, the batter's intent noted beside it, the fielder's position marked in the margin. The number I wrote at the top of that page was not 4 for 21. It was thirty — the thirty balls that remained after Dhir's dismissal, in which 69 runs were scored and not a single wicket fell.
The scorebook says one thing; the stadium said another. The book says the outstanding performance of the match belonged to a left-arm spinner who took four wickets and dragged his side to the edge of victory. The ground says that performance lasted fifteen overs, and that the match was settled in the last five, in which that spinner was not bowling.
This was the second T20 international of a five-match series. India had won the first and were set 181. New Zealand, batting first, made 180 for 5 — neither safe nor short on this ground. Nine point zero five an over across twenty overs, roughly a run and a half every ball. On a total like that, the side that wins is usually the side that takes a wicket or two through the middle and strangles the rate. The hosts had exactly one man for that job, and he happened to be the captain.
Santner carried a double load: captain, and the most trusted bowling asset in the XI. That combination produces a particular structural problem in T20 cricket, and I will come back to it at the end of this piece.
India's start was neither quick nor poor. Abhishek Sharma was on 27 when Santner had him caught at deep midwicket by Nathan Smith. What followed over four overs redrew the entire map of the Indian middle order. Shreyas Iyer, the captain, was bowled for seven — beaten by drift and flight as he tried to slog across the line. Axar Patel went for eleven, and his dismissal was a relay catch: Finn Allen intervened near the boundary and Daryl Mitchell completed it. Naman Dhir, whose 31 off 17 had briefly kept India's hopes upright, was the man dismissed by the flighted ball that opened this piece.
One clarification is necessary here, because the easy habit of reporting is to convert four wickets into four magic deliveries. Santner's four balls were not magic. They were balls built against a field setting and against a batter's intent.
Look at the anatomy. Abhishek Sharma caught at deep midwicket — the shot went straight to a fielder who was standing there because the captain expected that shot. Iyer bowled — the ball did not turn; it drifted and deceived the batter's sense of length. He cleared space for the slog, and the ball passed under the bat to hit the stumps. Axar's relay catch always means the same thing: the ball stayed in the air a long time, so the batter was beaten for pace, not turn. Dhir caught at extra cover — that fielder was placed there because the inside-out option was visible before the ball was bowled.
Three of the four wickets were catches, and all three went to positions the captain had already thought about. The scorebook credits the bowler; the chart says half the credit belongs to the field placement that induced the shot the batter should never have played.
Now the column the scorebook never carries. Four overs for 21 is an economy of 5.25. It means India never found, inside Santner's overs, the tempo a chase of 181 demands. When you need 9.05 an over across the innings, being held at 5.25 through the middle is not simply the loss of four balls. It rewrites the arithmetic of the whole match. On my page, Santner's four wickets sit in one column. Above them is another column, the one with the dot balls in it. The wickets were the consequence of that second column, not the cause of it.
For a few seasons now I have charted middle-over spin economy against India separately from everything else, because it is the passage of play that television highlights abandon first. The pattern that keeps returning is this: Indian middle-order batters arrive at the crease in a situation that demands a strike rate of 150 from the first ball. That is the hardest job in T20 batting, and it is the easiest prey any spinner will ever be handed. Santner took the prey.
Between Nagpur 2026 and Christchurch there is nearly a decade. In Nagpur he returned 4 for 11 — New Zealand made 126 for 7, bowled India out for 79 and won by 47. That surface turned. Christchurch did not. The difference is the key to this whole argument. Put the two spells side by side and the method is almost identical: the left-arm angle, the drift into the right-hander's pads, the repeated flight that forces the batter to re-price the length. What changed was the pitch. What did not change was the batter's intent.
Which is why the easy conclusion — that India are weak against spin — points the wrong way. Santner's record is not evidence of an Indian deficiency. It is evidence of the role the Indian middle order is forced to play. Any side's numbers four and five walk in during the eighth to twelfth over and try to hit from ball one, at precisely the moment the opposition's most experienced spinner is bowling to his most favourable field. The bowler usually wins that contest, and the scorebook records him.
There is another side to the record that is easy to skip. In men's T20 internationals, Santner is now the first bowler with more than one four-wicket haul against India. The achievement looks large and is genuinely rare, because taking four wickets twice against the same opponent requires a decade of playing that opponent, in that same role. Bowling roles in T20 shift fast; a spinner appears in the powerplay in one series and at the death in the next. Santner has stood in one place for ten years. That continuity is a story in itself, and it says something about a cricketer Indian coverage usually files away as a tidy economical spinner.
Now the part this piece was written for. After fifteen overs India were 112 for 6. They needed 69 off 30 balls — 2.3 runs per ball. A total like that can only be built by finding the boundary repeatedly, and a single dot ball pushes you further behind.
Tilak Varma finished unbeaten on 51 off 26. Nitish Kumar Reddy finished unbeaten on 26 off 13. An unbroken seventh-wicket stand of 69 off 30 balls, and the target was reached with one ball to spare.
Put those three numbers side by side and a pattern emerges that the scorebook leaves scattered across separate lines. Tilak's strike rate was roughly 196. Nitish's was roughly 200. This was not the partnership in which one batter holds and the other hits. Both had to travel at about two runs a ball, because at a required rate of 13.8 an over there is no room left for an anchor. The traditional chase template — one batter at 120, the other at 180 — simply does not survive an equation like 69 off 30. Both men had to run at double speed at the same time, and they reversed the arithmetic of fourteen overs in thirty balls.

One more thing about that stand: it never looked like breaking. A batter starting at 112 for 6 carries the fear of losing, and a shot played out of that fear usually goes aerial. New Zealand's fielding standard in this match was high — Axar's relay catch is the cleanest proof of it. Which means the hosts did not lose the last five overs by dropping a catch. They lost them because they had no wicket-taking option left for those thirty balls.
This is where the view from outside makes its easiest mistake. The standard reading after the game will be that Santner's spell was almost enough and that India escaped. The picture from the ground runs the other way.
Santner's outstanding figures were New Zealand's biggest structural problem. A captain who is also his side's best bowler finishes his four overs by the time he is needed most. Santner's fourth over was the fifteenth. After that, the last five overs were bowled by men who did not have a single wicket in the match. The death overs are the most expensive passage in T20 cricket, and the man who had settled the first fifteen was left standing at mid-off for the last five.
There is a subtler layer to this. The scoreboard reading 112 for 6 in the fifteenth over was the most dangerous number of the evening for the home side, because it was telling them the match had been won. The wicket that looked like the kill was the one that loosened the home side's grip. Dhir's dismissal was necessary — his 31 off 17 was keeping the rate alive — but the two batters who followed arrived with no memory of the collapse, only a calculation of what had to be hit. And New Zealand had no fresh weapon left to stop them.
Somewhere up in the stands at Christchurch, after the fifteenth over, a pattern started to breathe — the pattern that returns in every match where the captain is also the frontline spinner.
Watching South African cricket has always made one comparison useful to me. In the SA20 the middle-overs spinner is the captain's most trusted instrument, because the grounds are large and the ball holds — a spinner's price there is set by his control. The IPL auction speaks a different language: a spinner's value is set by his death overs, because those are the overs that get sold to television afterwards. Santner's role belongs to the first category, and his greatest record has come from it. The question I am asking, not answering, is this: are we measuring properly the spell that settles the most important part of a match and then disappears from the highlights?
Honesty is required here, because working on domestic and under-covered cricket means guarding against my own habits. It is easy to turn one fine spell into an entire thesis. This is one match, one spell, one defeat. Finding more meaning in it than that is the same haste I have tried to avoid. What Santner did was rare and should be left rare.
India lead the series 2-0 with three to play. My chart for the third match will watch three things. First: whether Santner keeps an over back for the sixteenth to eighteenth, or whether the old habit of captaincy finishes him by the fifteenth again. Second: whether India's middle order changes its entry plan — whether numbers four and five ask for two or three balls of grace instead of attacking from the first. Third: whether New Zealand hold a separate bowler for the last five overs, whatever his name is.
I kept the chart long after everyone went home. On that page there was one more line drawn under the 4 for 21, and that line belonged to the last thirty balls. Before the next match arrives, a question forms itself: how do we record the spell that won the first fifteen overs and lost the last five — as a fine performance, or as a bowling plan caught inside its own clock?
