Zeeshan Ansari's 5/45 and UP's 140-run lead: the real arithmetic of Green Park
**मुख्य उत्तर:** उत्तर प्रदेश ने रणजी ट्रॉफी ग्रुप मुकाबले में गोवा के खिलाफ पहली पारी में 38 रन की बढ़त ली और दूसरे दिन स्टंप्स पर 102/4 पर 140 रन आगे था। ज़ीशान अंसारी ने 15 ओवर में 45 रन देकर पांच विकेट लिए, जबकि रिंकू सिंह ने 118 रन नाबाद बनाए। **मुख्य तथ्य:** - गोवा की पहली पारी 61.3 ओवर में 164 रन; रन रेट 2.68 — सतह पर स्कोरिंग की कठिनाई का सबसे साफ़ संकेत। - ज़ीशान अंसारी: 5/45, इकॉनमी 3.00, स्ट्राइक रेट 18.0 गेंद प्रति विकेट, औसत 9.00। - रिंकू सिंह का 118* यूपी के 202 रन का 58.4 प्रतिशत; दूसरी पारी में 102/4 पर 89.2 प्रतिशत रन शीर्ष क्रम से। - यश कसवणकर: यूपी की पहली पारी में पांच विकेट, दूसरी पारी की पहली चार गेंदों में दो विकेट। - सुयश प्रभुदेसाई: 71 गेंदों में 19 रन, स्टंप आउट — धीमी सतह का मात्रात्मक प्रमाण। **स्रोत:** मूल मैच रिपोर्ट के 33 सूचना बिंदु (स्टेज-1 डीकंस्ट्रक्शन)। स्रोत सामग्री में प्रकाशन तिथि और बायलाइन दर्ज नहीं; कई आंकड़े सत्यापन-लंबित हैं। **संबंधित प्रश्न-उत्तर:** प्रश्न: ग्रीन पार्क की पिच पर किसका दबदबा रहा? उत्तर: पहले दिन नई गेंद पर सीम और दूसरे दिन से स्पिन — यही दो-चरणीय बदलाव इस मैच का असली ढांचा है। प्रश्न: ज़ीशान अंसारी की वापसी कितनी टिकाऊ है? उत्तर: दो मैचों में दो पांच-विकेट हॉल और एक अर्धशतक मज़बूत है, पर चार साल के अंतराल की वजह अपुष्ट है और यह प्रदर्शन अपने ही मैदान पर आया — cricsultan.com Player Depth Index जैसे निरंतरता-संकेतक ही इसे सही संदर्भ देंगे। प्रश्न: यूपी की 140 रन की बढ़त कितनी सुरक्षित है? उत्तर: अनुकूल, नियंत्रित नहीं — दूसरी पारी की पहली चार गेंदों में दो विकेट गिरना दिखाता है कि टॉप ऑर्डर अब भी असुरक्षित है।
Suyash Prabhudessai faced 71 balls and scored 19. That line does not make a headline. But when I opened the scorecard at stumps on Day Two at Green Park, Kanpur, my eye stopped at 19 off 71 before it reached Zeeshan Ansari's 5/45. Five wickets is an announcement; 19 off 71 is a question. And the question is how hard run-scoring actually was on that surface.
Goa made 164 in 61.3 overs. A run rate of 2.68. That number explains the conditions better than any adjective about a spin-friendly pitch ever will. I have read domestic first-class scorecards this way for years — total first, then overs, then run rate. Totals lie; overs usually don't. When a side bats more than sixty overs and still cannot reach 170, the story is in the surface, not in a single shot.
Uttar Pradesh look comfortable at stumps: a 38-run first-innings lead and 102/4 in the second, 140 ahead. This piece exists to audit that comfort. A 140-run lead at Kanpur is not the same asset as a 140-run lead anywhere else, and Ansari's 5/45 is the return of a leg-spinner who has not bowled in the Ranji Trophy for four years, taken at his own association ground. Both facts are true. The story being attached to them is a separate question.
The ground, the surface, and those 38 runs
Green Park carries a specific reputation in Indian domestic cricket: low bounce, a surface that slows as the match ages, and one that tilts further toward spin with every session. The original report notes that the pitch was already assisting spin on the morning of Day Two. That sentence looks minor. The entire architecture of this match rests on it. If the surface began changing that early, a fourth-innings target of 200 at Green Park is a materially different ask from 200 on a flat deck.
Day One looked different. Five of UP's first-innings wickets went to Goa's seamer Yash Kasvankar. That detail is mentioned in passing, and it is the most under-read line in the report. A surface described as spin-friendly produced a five-wicket haul for a seam bowler. The straightforward reading is that the pitch was not uniform: the new ball and seam movement belonged to Day One, spin to Day Two onward. Painting a pitch one colour for four days is a convenience of reporting, not a description of cricket.

UP's first innings ended at 202. Rinku Singh made 118 not out. The other ten batters contributed 84 between them. I call that a dependency ratio. 58.4 per cent of the first innings came from one batter. In the second innings the pattern repeated: Aryan Juyal 60 not out and Karan Sharma 31, which is 91 of 102 — 89.2 per cent — from two players. Twice in two innings, the same shape. That is not coincidence; it is a team-construction problem, and a favourable result will hide it comfortably.
Zeeshan Ansari: how the wickets fell matters more than how many
Ansari's figures are clean: 15 overs, 45 runs, five wickets. Economy 3.00, a wicket every 18 balls, average 9.00. On a surface running at 2.68 an over, conceding 3.00 with five wickets attached is control, not leakage. But the useful information is not in the numbers; it is in the modes of dismissal.

Prabhudessai was stumped after surviving 71 balls. Shivendra Bhujbal, on 44, was caught and bowled at the point the innings began to break. Both modes say Ansari was beating batters in the air, not merely exploiting the surface. On a rank turner, wickets usually arrive lbw, bat-pad, or caught at slip and short leg, because the ball turns before the batter can commit and defence becomes the default. A stumping happens when a batter comes out to a big shot and the ball is slowed through the air. A caught-and-bowled usually comes from a leading edge induced by flight or a change of pace. Both describe a bowler manufacturing a false shot.
Ansari's own explanation points the same way: he kept hitting his line and length to tempt batters into big hits. It is easy to file that under cricketer cliché, but on a slow surface it is technically accurate. When a pitch is too slow to beat a batter for pace, the wicket has to come from a mistake. An economy of 3.00 alongside a stumping and a caught-and-bowled is consistent with that method.
One caution, applied to myself first. This is a reading of one innings, not a career verdict. Ansari took five wickets and made a fifty against Bihar in the season opener. Two five-fors and a fifty in two matches is a genuinely strong run. Indian domestic cricket also has a long history of two-match explosions that convert into nothing. The correct phrase is not "he is back" but "he belongs on a tracking brief." My own rule is to reassess after six first-class innings.
Now the part the report treats as colour. Ansari is returning after a four-year absence from the Ranji Trophy. Analytically, that is the central unexamined variable. A four-year gap has three possible causes — injury, form, or selection — and they lead to entirely different projections. If it was injury, the current workload of 15 overs plus batting is the specific stress test, and a missed fixture in the next three or four rounds would be the tell. If it was selection, the question moves to state-association priorities. If it was form, this is the least durable kind of comeback. The report offers no answer, and every positive projection built on it is standing on an unchecked foundation.
One more piece of context. For a spinner, the late twenties into the early thirties is usually the ascending part of the age curve, not the descending part. If Ansari sits in that band — his exact age is not stated — the four-year gap cost him his peak development years rather than arriving at the end of his career. That makes the current window more significant, not less. It is an inference, and I will label it as one.
Rinku Singh's 118*: the innings is real, the attention is an artefact
Rinku's century is the most-read fact in this report and the most misread. A batter whose public identity is T20 finisher made 118 not out in four-day cricket, 118 of his team's 202. That is a genuine red-ball data point. His career first-class average is reportedly in the fifties (not stated in the source; verification pending). If accurate, this innings confirms his red-ball record rather than deviating from it.
Two errors are available here, and they point in opposite directions. The first is treating one innings as evidence of a format conversion. A single first-class innings does not translate across formats in either direction. The second is presenting the innings as a Test case. Indian selection discourse separates formats far more sharply than the coverage of an innings like this implies, and that separation is healthy.
The attention attached to this innings is a function of the name, not the innings. An identical 118 not out from an uncapped batter would have generated a fraction of the coverage. The innings is real; the noise around it is a media event. Keep the two in separate ledgers, or within a month someone will report that Rinku has proved himself for Test cricket.
There is a structural layer here too. A player of Rinku's profile batting long innings in four-day cricket during the Ranji window carries injury exposure his franchise would treat as unpriced risk. Hours at the crease in red-ball cricket sit awkwardly against white-ball market value. That is a tension in the Indian calendar, not a story in this match.
Yash Kasvankar: the most under-reported performance in the match
If I am asked who produced the best individual performance in this game, my answer is not 5/45. Yash Kasvankar took five wickets in UP's first innings — the same innings in which Rinku finished 118 not out. Then he removed Goswami and Kaushik inside the first four balls of the second innings.
This is not a consolation prize. A seamer taking five on a pitch the report frames as spin-friendly, then breaking the top order with the second new ball, is the outstanding contribution of the match — and it came from the side that is behind. The original report disposes of it in a single line. That is a distortion of the picture, not a shortfall in the player.
Its analytical value is that it breaks the easy story about the pitch. If the surface had been a spinner's track from ball one, Kasvankar would not have five. If it had been a seamer's track, Ansari would not have five in 15 overs. The truth sits in between and moves with time: seam with the new ball on Day One, spin from Day Two. Two batting line-ups faced two different challenges on the same square.
Goa's collapse: conditions or technique
Goa resumed at 43/0, reached 61/0, and then lost nine wickets for 103 to be bowled out for 164. The report attributes it to wickets at regular intervals and no partnership being allowed to develop. That is accurate as description. There is a better way to read it.
This is a concentration failure, not a conditions event. Going from 61/0 to 164 all out was not caused by one unplayable delivery, a run-out, or a disputed call — no such factor appears in the text. When nine wickets fall to sustained pressure with no partnership forming, the problem is the ability to rotate strike against spin. On a slow surface that weakness surfaces first, because you cannot generate pace through the ball; you have to work it, take singles, and force the bowler to change his line.
Three of Ansari's five wickets were batters dismissed for single-figure scores — 0, 9 and 6. That points to a lower order with limited spin defence, which is why crediting the surface alone would be premature. Bowling and batting both contributed. I built the spreadsheet first; the story arrived in the empty rows — and in this match the empty rows are Goa's sixth to eleventh.
The 140-run lead: worth more than the number
Here is the arithmetic the report does not do. A fourth-innings target at Kanpur should be above 200, because the surface has been taking spin since Day Two and the ground is known for deteriorating bounce. A target of 200 at this venue is harder than the same 200 on a flat pitch. That is the single most important tactical read of the match, and the source does not state it.
The same logic cuts the other way. At 102/4 with six wickets in hand and 140 ahead, UP are favourably placed, not in control. The distinction is not semantic: two wickets in the first four balls of the second innings is a reminder that the top order is not secure. If UP are bowled out for 180, the target sits near 220 and Goa's door is open. A draw is the least probable outcome here — two fragile batting sides and a Day Four surface point to a result.
And the largest information gap in the report deserves to be named. There is nothing on Goa's second-innings spin resources. That silence is the report's biggest shortfall, because it determines whether 140 is defendable. A side that loses nine for 103 under spin pressure may not have the attack to reproduce that pressure in the fourth innings — which would make UP's lead more robust than it looks. That is inference, not information.
The contrarian read: the cost of the word "command"
This is the point I have been holding back. The body of the original report is careful — it notes the surface, names the supporting bowlers, and records UP's second-innings wobble. The headline compresses all of it into the claim that Ansari spun UP into command. The scoreline does not support the word.
There is a larger structural issue underneath, and it is bigger than this match. Building a home-conditions spin attack is the rational domestic strategy for a state side — it is the cheapest and most reliable model in Indian cricket. It also carries a cost: it systematically produces statistics that do not travel. Five wickets at 3.00 an over on a surface running at 2.68 is a bowler doing his job. Calling it a comeback sets a low bar. Domestic spin records deserve a discount, and the discount comes from the structure of the competition, not from the honesty of any player.
The inverse applies to Goa. Everyone is looking at 164. I am looking at the fact that they were 61/0. A side that goes from 61/0 to 164 all out has a pattern problem, not a pitch problem — and patterns repeat across a season. Judging either team's tier from one group fixture is the least reliable sample domestic cricket offers.
One reporting-quality note. The name Vasuki Koushik appears as a Goa batter; it is a name associated with Karnataka in Indian domestic cricket. If it is the same player, that is an inter-state transfer, which is permitted — but the report does not say so. The identification is unconfirmed and I will not treat it as fact. The omission itself is a signal: player background has become a luxury in domestic reporting, when it is precisely what gives the reader context.
What to watch next
This ends with a prediction, because a summary is of no use to anyone. This entire read is wrong if UP are bowled out for under 180 on Day Three and Goa chase something under 220 with four wickets in hand. In that case the surface did not decide the match; UP's top order did — and that, not Ansari, is the real story of this team.
On Ansari, three items sit on my tracking sheet. His availability across the next three or four rounds — a single missed fixture and the four-year gap was physical. His figures away from Kanpur — an economy above 3.5 or fewer than two wickets an innings and the home-conditions discount is confirmed. And a review trigger at six first-class innings.
On Rinku, one measure: a second three-figure score this season, or a sustained average above fifty. That would make the red-ball case real — narrow, but real. On UP: the first- and second-wicket partnerships across the next three innings. Repeatedly under fifty and the team is carrying a structural weakness into a campaign it may still win matches in.
The bell lap is not the finish; it is where the pattern becomes visible. Stumps on Day Two at Kanpur is that place. The scorecard says 140, the surface says 2.68, and the first four balls of the second innings say something else again. Trusting any one of them is easy. Reading all three together is the only way into this match.
