होमAsian CricketWellington rain, Siraj's availability and Tickner's workload: the ledger the second ODI scorecard will not open

Wellington rain, Siraj's availability and Tickner's workload: the ledger the second ODI scorecard will not open

**मुख्य उत्तर:** भारत और न्यूजीलैंड के बीच पाँच मैचों की वनडे सीरीज़ का दूसरा मुकाबला वेलिंगटन में बारिश से प्रभावित है; भारत ने अभ्यास सत्र रद्द किया और मोहम्मद सिराज की उपलब्धता से गेंदबाजी संयोजन पर अनिश्चितता बढ़ी है। **मुख्य तथ्य:** - भारत बनाम न्यूजीलैंड, पाँच मैचों की वनडे सीरीज़ का दूसरा मुकाबला, वेलिंगटन; मैच की तारीख स्रोत में दर्ज नहीं है। - भारतीय टीम ने बारिश के कारण बाहरी अभ्यास सत्र रद्द किया; न्यूजीलैंड ने अभ्यास इनडोर हॉल में किया। - दोनों टीमों ने 5 नवंबर को यात्रा की और उसके बाद केवल एक अभ्यास सत्र मिला। - मोहम्मद सिराज इंडिया A की प्रतिबद्धताओं के बाद टीम से जुड़े; अंतिम एकादश की घोषणा नहीं हुई। - ब्लेयर टिकनर शीतकालीन चोट से उबर रहे हैं; अभिषेक शर्मा की 38 गेंद में 113 रन की पारी का प्रारूप अस्पष्ट, स्ट्राइक रेट 297.37। **स्रोत:** Stage-1 मीडिया सामग्री; मूल प्रकाशन और प्रकाशन तिथि निर्दिष्ट नहीं | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर:** **प्रश्न:** क्या मोहम्मद सिराज दूसरे वनडे में खेलेंगे? **उत्तर:** सिराज की उपलब्धता की पुष्टि हुई है, लेकिन अंतिम एकादश की घोषणा नहीं हुई, इसलिए चयन अनिश्चित है। **प्रश्न:** अभिषेक शर्मा की 113 रन की पारी को वनडे फ़ॉर्म का आधार माना जा सकता है? **उत्तर:** नहीं, क्योंकि उस पारी का प्रारूप स्रोत में स्पष्ट नहीं है और क्रिकेटर की वनडे प्रदर्शन श्रृंखला उपलब्ध नहीं है। **प्रश्न:** बारिश का मैच पर सबसे बड़ा असर क्या होगा? **उत्तर:** बारिश से मैच छोटा होने पर डीएलएस लागू हो सकता है, जिससे पावरप्ले का महत्व बढ़ेगा और चयन की प्राथमिकता बदल जाएगी।

The drizzle arrived in Wellington on the evening before the second ODI, exactly as forecast, and India's outdoor session was cancelled. New Zealand moved theirs indoors. On the surface this is a small administrative difference — one side did not set up nets, the other took their sweaters off under a roof. Read as a ledger entry, it is not a difference at all. It is a posting, and the only question that matters is which account it lands in.

I learned on the Manchester City training-ground beat nine years ago that the session before a match is never about the sport. It is about weather, ground and body. In Wellington two of those three sit outside anybody's control, and the third sits with the team management alone. When a session is cancelled, the loss is not time. It is measurement — and measurement is priced differently for each team.

First, the file check

The material behind this analysis carries no named original outlet, no publication date, no official team sheets and no match result. The match day is given only as "Saturday". That is not a small gap. It is the gap that determines how much of what follows can be trusted.

So every figure here will carry its own provenance, and anything unsourced will be labelled insufficient rather than estimated. When I worked the Erling Haaland release-clause story in spring 2026, nothing went out until three sources had confirmed the €60 million structure and the five-year term. The same rule applies. The difference is that then the number was a clause; here it is a count of overs, and those have not yet been bowled.

One warning belongs at the front of this file rather than the back. Abhishek Sharma's 113 from 38 balls cannot be treated as ODI evidence. The format of that innings is not established in the source material. This is the most recycled error in touring journalism — turning a T20 score into a fifty-over credential. I am not going to make it.

Context: five matches, one session, two sets of dimensions

This is the second of five bilateral ODIs. Both teams travelled on 5 November and were given a single practice session afterwards. In a five-match series that arithmetic is unforgiving: recovery, video work and skill-specific practice compete for the same handful of hours. India gave their hours up. New Zealand relocated theirs.

The ground information in the source is thin but usable — Eden Park's straight boundary is short, while Wellington's square boundary is the shorter one. An honesty note is needed here. The source names the Wellington venue "Hnry Stadium", which is clearly garbled and is most likely a corruption of Sky Stadium. When a name cannot be verified I trust the dimension instead, because a dimension has a direct relationship with the scorecard and a name does not.

A short square boundary in Wellington means the risk arithmetic of the pull and the cut is different from Auckland. A full length that is expensive through the straight lines at Eden Park can disappear square of the wicket at Wellington. The source supplies no wind direction and no pace data, so I will not go further than the evidence allows. But this much holds: a bowling plan that worked in Auckland will not transfer to Wellington unchanged, and that is precisely where a cancelled session becomes expensive.

There is a strong rain forecast for match day. That is operational information, not tactical, and operational information usually decides more than tactics does.

What a cancelled session actually costs

An outdoor session measures three things: the drag and direction of the wind, the quality of sight — cloud height changes how swing is perceived — and the grip underfoot. An indoor hall can approximate the third and none of the first two. When a bowler says the ball would not carry in the air, that is not a reading. It is an experience that becomes tomorrow's decision. India no longer have it.

But the correction matters, or we drown in procedure. In ODI cricket a lost session costs less than in T20, because fifty overs give a player time to repair. A bowler with the wrong length in the first spell can find it in the third. A batter who misread the wind off ball one can read it by over ten. T20 offers no such repair window, which is why a washed-out session there is fatal. India's loss is real; it is not as large as the headlines are making it.

The real loss sits in a different account. A side with a settled plan is barely moved by a cancelled session — it only has to execute. A side carrying an unresolved question is moved a long way, because the question never got tested on grass. India's cancellation is expensive because their biggest question is not about how to play but about whom to pick — and selection questions get answered in the nets, not at the captain's desk.

A dimension is a bowling instruction

Boundary distance does not change a captain's decision. It changes a bowler's length. A short square boundary at Wellington means the "good length" for a fast bowler is not the length in the coaching manual.

Three consequences follow. A short square boundary raises the value of the cut and the pull, which pulls a fielder out of the inner ring to protect the square boundary, which opens the singles market — and that is the chain usually dismissed in commentary as "field settings" when it is really an entire economy: the price of a wicket against the price of a run.

Second, the slower ball and the cutter behave differently. A delivery that landed inside the rope in Auckland can land on it in Wellington — but square, not straight. The bowler changes line, not pace.

Third, and least discussed, a short boundary changes a fielder's mind. When the rope is close, a fielder does not dive; he blocks. And when he blocks, twos are taken that never appear in a scorecard as good running but do appear in the result.

I count the drills before I trust the tempo of the match. If India have not adjusted their line to Wellington's dimensions, the fifty runs in the first fifteen overs will come off the edges of cuts and pulls rather than from any stroke, and the credit will belong to a decision nobody made out loud.

Siraj versus Nabi: availability is not selection

Mohammed Siraj has joined the squad after completing his India A commitments. The source confirms he is available. It does not confirm he will play. That gap looks small and is not.

There are three separate levels and conflating them is the commonest error in team news: availability, eligibility and the final XI. The source confirms the first two and is silent on the third. Until the official XI lands, every argument about Siraj is an estimate, and calling an estimate an estimate is the job.

The same question runs on the other side. "Nabi" appears in the source as a possible competitor, with no role, no spell length and no recent numbers attached. I cannot enter a player into the ledger on a "possibly X". Selection arguments need a role before they need a name.

So what is the case for Siraj, if the numbers are absent? It rests on three things, and all three sit outside the sport.

Wellington rain, Siraj's availability and Tickner's workload: the ledger the second ODI scorecard will not open

Experience as insurance. Across five matches, a senior quick is the policy that pays out in match three when a younger bowler's workload runs out. Picking Siraj is not a one-match decision; it is series-wide risk cover.

Control with the new ball. Wickets in the first ten overs are worth more than wickets in the last ten because they change the shape of the whole innings. But I cannot quote a single figure for this match — the source gives no average, no economy and no record in New Zealand. Experience is a quality, not a statistic, and the two cannot share a column.

And the third, the least discussed: rain. If the match is shortened, the selection logic inverts. A reduced game does not want a fifth bowler; it wants three quicks and two spinners who can compress twenty overs. Rain does not merely spoil cricket — it reverses the priority order of selection. A side that treats weather as background while picking an XI has done half the job.

Tickner's overs ledger

Blair Tickner is the most honest part of this file because he is doing his own reporting. He is recovering from winter injuries, wants to build his bowling workload, hit four sixes in Auckland, and now wants to improve with the ball.

Discipline is needed here, and it may be the most useful paragraph in this piece. Four sixes are a boundary count, not a form certificate. We do not have his total, his balls faced, the circumstances of his dismissal or the context of the innings. Four sixes establish a lower-order weapon. They do not establish repeatable run-scoring.

More important is the systemic point buried in his comment: he describes managing bowling sessions because players move between international commitments and Test cricket. That is not a personal excuse; it is a structural admission. When a player rotates through three formats and two domestic competitions, no medical staff can save him from two games a week. A physio can treat an injury. He cannot rewrite a calendar.

Tickner's workload is a signal to be read three ways, and all three can prove me wrong. Bowl his normal four spells and New Zealand have judged the recovery complete. Bowl two and it is injury management, with depth questions attached. Not play at all and half the tactical analysis written in advance is cancelled. So I will watch the over count and then his availability for the next fixture. That tells me more than an average, because overs are the actual load and an average is only the outcome.

297.37: a number that needs a red flag

Now the most dangerous figure in the file. Abhishek Sharma, 113 off 38. I did the arithmetic: 113 ÷ 38 × 100 = 297.37.

That is extraordinary, which is exactly why it needs handling. An extraordinary number produces the most wrong conclusions, because it stops asking questions and starts answering them.

Which questions? What format was the innings played in — the source is silent. On what pitch — it says only "the referenced venue". Against what bowling — unknown. Does his ODI career average or strike rate correspond — not supplied.

Wellington rain, Siraj's availability and Tickner's workload: the ledger the second ODI scorecard will not open

Without those four answers, 297.37 describes a performance; it does not certify a capacity. And in ODI cricket the measure of capacity is not strike rate. It is the ability to last fifty overs. A batter who can make 113 from 38 should be asked why he did not make 113 from 138, and nobody is asking.

Rain, DLS and the price of the new ball

The source records persistent drizzle and a strong match-day forecast. No innings has happened, no target has been revised, no abandonment has occurred — so there is no DLS controversy in existence. But the framework is present and it changes decisions.

Three things change in a shortened match, and no captain writes them into the plan in advance.

The price of an over. When fifty becomes thirty, a containing bowler loses his function; you need wicket-takers because wickets are the resource DLS prices. That is why a forecast of rain raises the value of a Siraj even if he is expensive.

The weight of the first ten overs. In a thirty-over match the Powerplay is a third of the contest. A good opening spell can win it; a bad one leaves you handing the game to a spreadsheet. Repino taught me that a set piece is a ledger with legs: you count the rehearsals, then make the execution pay against them. A Powerplay is that set piece, and rain cuts its over-quota, which cuts the tolerance for error.

And the psychology of a revised target, the least understood of the three. When the target shrinks, the chasing side's risk arithmetic inverts: a wicket costs more because there are fewer balls to replace it. A batter who could have built an innings over fifty overs is forced to play at 130. Rain does not help one team here. It leaves both half-prepared.

New Zealand's early-wicket policy

Tickner states the priority plainly: early wickets. In ODI cricket that is a statement, because most sides choose control with the new ball and hold the wicket-taking for the second spell.

Three possible executions exist and the source does not choose between them: swing, with catchers in and two slips; the short ball, which is a high-risk play on a ground with a short square boundary because it raises the pull coefficient; or an attacking field with the line pushed up to force the drive. All three share a premise: New Zealand do not want India's top order to have time, and that is specifically rational here because India have had so little preparation. A batter who did not train outdoors yesterday can have slow feet for a few dozen balls. That window is the whole bet.

But I have to doubt my own argument. If rain shortens the match, an attacking start becomes riskier, because four overs for twenty runs leaves no time to repair. Attack is a luxury you can only finance across a full match; in a shortened one the same attack becomes a gamble. New Zealand's policy was built for an October ODI, not a wet one.

The outside misreading

From outside, the story of this match is being written as: rain wrecked India's preparation, New Zealand gained home advantage, and India must now pick Siraj to be safe. All three assumptions are weak and all three come from the same error — filing weather under advantage.

Rain does not help the home side. It deflates the value of local knowledge. New Zealand's edge is that their players know when the Wellington wind turns and when the ball stops carrying. That knowledge compounds over fifty overs, not thirty. When a match is cut, the interest on experience falls and the value of raw talent rises. Rain does not enlarge a home advantage; it truncates it.

Second, a cancelled session hurts not the side playing badly but the side with a decision still open. India's real question is the bowling combination — who takes the new ball, who bowls the death, when the spinner comes on. That question is not settled in an indoor net. It settles itself in the first ten overs. India's loss is one of time, not of strategy.

Third, and least comfortable: folding Tickner's four sixes and Abhishek's 113 into a single story called form. Different formats, different contexts, different roles. A story assembled by joining two unrelated numbers is not reporting. It is montage. I do not file montage.

The forward signal

Wellington's real scorecard will not be the one on the screen. It will be how many lines changed in the first ten overs, how many overs Tickner bowled and whether he is available for the next fixture, whether Siraj got the new ball or the death, and where Abhishek Sharma was sent in.

The lesson I keep from Manchester is that the grass remembers every rep and my job is to write it down. Wellington's rain may erase the scorecard. It will not erase the cancelled session, the overs distribution or the delayed XI. Those decisions will return one at a time across the remaining four matches of this series. The question is not what the weather will do in Wellington. It is whether either side opened the right ledger for it beforehand.

संबंधित खिलाड़ी