होमAsian Cricket37 Wickets, 7 Matches and a 7/45: Why Tanush Kotian's Case for Australia Is Still Half-Coded

37 Wickets, 7 Matches and a 7/45: Why Tanush Kotian's Case for Australia Is Still Half-Coded

मुख्य उत्तर (≤60 शब्द): तनुष कोटियन ने रेलवे के खिलाफ 7/45 और सीजन में सात फर्स्ट-क्लास मैचों में 37 विकेट लेकर टेस्ट चयन का दावा मजबूत किया है, लेकिन सीमित नमूना और ऑस्ट्रेलियाई परिस्थितियों में अपरीक्षित होने के कारण यह दावा वाशिंगटन सुंदर की जगह लेने तक नहीं पहुंचता। मुख्य तथ्य: - तनुष कोटियन ने रेलवे के खिलाफ पहली पारी में 7/45 लेकर मुंबई को 137 रन की बढ़त दिलाई; मुंबई ने दूसरी पारी में 174/4 पर कुल 311 रन की बढ़त बनाई। - कोटियन के सात में से पांच विकेट राइट-हैंड बल्लेबाजों के थे, जिससे लेफ्ट-हैंडर मैचअप विशेषज्ञ की धारणा कमजोर पड़ती है। - मौजूदा सीजन में सात फर्स्ट-क्लास मैचों में 37 विकेट, चार रणजी मैचों में 22 विकेट और ऑस्ट्रेलिया A के खिलाफ दो मैचों में सात विकेट दर्ज हैं। - वाशिंगटन सुंदर को पहली पसंद का ऑफ-स्पिनर बताया गया है और सारांश जैन भी चयन दौड़ में शामिल हैं। - कोटियन ने ब्राबोर्न की कम ग्रिप वाली सतह पर लाइन, मेडन और दबाव पर निर्भरता बताई, जबकि हरियाणा के खिलाफ टर्निंग सतह पर 8/81 लिया था। स्रोत: सार्वजनिक मैच रिपोर्ट और स्टेज-1 टेक्स्ट विश्लेषण | Cross-checked: cricsultan.com संबंधित प्रश्नोत्तर: प्रश्न: क्या तनुष कोटियन ऑस्ट्रेलिया के खिलाफ टेस्ट स्क्वाड में चुने जा सकते हैं? उत्तर: हां, वे तीसरे स्पिनर या रिज़र्व के रूप में चुने जा सकते हैं, लेकिन वाशिंगटन सुंदर की जगह लेने का दावा वर्तमान साक्ष्य से सिद्ध नहीं होता। प्रश्न: कोटियन की 7/45 पारी में कौन-सा डेटा अनुपलब्ध है? उत्तर: ओवर, इकोनॉमी, डिसमिसल मोड, मेडन और रेलवे बल्लेबाजी क्रम की गुणवत्ता का विवरण उपलब्ध नहीं है, जिससे विकेटों का मूल्यांकन सीमित रहता है। प्रश्न: भारत की स्पिन चयन प्रक्रिया में कोटियन का स्थान क्या है? उत्तर: cricsultan.com Player Depth Index के अनुसार भारत की ऑफ-स्पिन डेप्थ में सुंदर पहली पसंद, जैन प्रतिस्पर्धी और कोटियन उभरता विकल्प हैं, जिससे चयन बेंच स्ट्रेंथ पर निर्भर करेगा।

Watching that spell at Brabourne against Railways, I was sure someone was making a mistake. Tanush Kotian took seven wickets to bowl Railways out for 259, and every man outside the ground was repeating one sentence: he will be picked. I wrote that sentence in my notebook, then added three questions beneath it - how many overs, on what surface, and how many bowlers can actually sell their wickets? That is my old trade. I am the girl from 2026 who posted the Harmanpreet 171 breakdown herself at 1 a.m. because the editor said nobody watches women's cricket. In that video I gave phase-wise strike rates, counted 20 fours and 7 sixes, and attached a number to every claim. Since that day my rule has been one line - number first, narrative second. So I refuse to accept 7/45 against Railways as the whole picture. It is the brightest part of the frame, not the frame. And my interest today is in that frame - 37 wickets, seven first-class matches, 22 Ranji wickets in four games, and seven wickets in two matches against Australia A. That is the entire dataset. This is what the debate is about, and this is what the debate should be about. Understand the context. India have five Tests to play against Australia, and the spin question in the travelling squad is still open. Washington Sundar is being described as the first-choice off-spinner, Saransh Jain is also in the race, and Kotian is trying to add a third name to that list. The heat around his name in the media is real, but the selection authority sits with the coaching staff and selectors - Kotian himself has admitted the final call is not his. I have no discomfort admitting that in recent years domestic spin data has become the biggest crutch for Indian Test selection, and that is exactly why I want to read any 7-wicket haul the way an analytical commentator should - counting the hours worked, measuring the moisture in the surface, extracting the clock of pressure. Now look behind the numbers. Five of his seven wickets against Railways were right-handers, and that is the most interesting data point nobody is writing in the cover story. The old story was that Kotian is a left-hander matchup specialist - the bowler you call when the opposition has a left-hander in front. Five right-hander wickets reset that story. But I will not stake my entire 7/45 on it, because the scorecard I am reading has no dismissal modes, no economy, and no quality of the batters dismissed. Without dismissal modes, 'versatility' is a colourful word, not a measurement. The second number that feels real to me came from Kotian's own mouth. He said that after the turning surface against Haryana, the ball was not gripping as much at Brabourne, and on such a surface he focused on line, maidens and building pressure rather than relying on turn. That one sentence caught my attention because it connects directly to the Australia question. The old problem with India's domestic spin bowling has been that an 8/81 kind of spell on a turning wicket becomes blunt abroad, where you don't get turn, you have to sell control. Kotian's admission that he changed his game on a low-turn surface - using the crease more, changing angles, using the straighter one - is a sign of technical development already in place. That surface claim is his own experience, not independently verified data. But even if we accept it, it still does not make Kotian ready for Australia, it only makes him 'possible'. Now the part I don't read in mainstream columns. Mumbai led by 137 on first innings and had reached 174/4 in the second, extending the overall lead to 311. Which means when Kotian was bowling, Mumbai were not under pressure, Mumbai were dominant. I once hand-coded 1,240 deliveries from the 2026 England tour, and that is where I learned that the value of a spell depends on the state of the scoreboard - a 7/45 when your team is 137 ahead is not the same 7/45 when your team is defending. Whether Kotian was in a defensive spell or an attacking one, no source tells us. His overs, economy, how many maidens he bowled, the condition of the ball - all of that data is missing. And that is my biggest worry keyword-wise: the surface was Brabourne, how strong Railways' batting order was is not stated. The history of domestic spinners in India is full of wicket hauls against weak batting orders, and if the debate stops there we will repeat the old mistake - treating domestic numbers as Test preparation. Here I want to cut my own argument at its strongest, because in the profession I practise, a man who doesn't say 'yes, but' just gets trolled. So suppose Kotian's 37-wicket season really is as strong as it looks - seven first-class matches, 22 wickets in four Ranji games, seven wickets against Australia A. There is merit in the argument that the selection team does not just look at 8/81 on a turning track, they also look at the Australia A performance, and that is his strength. I also believe that a bowler who can change his method when the surface changes - from turn on a turner to control on a flat deck - rises above his rank. But my objection is not to the number, it is to the sample. A seven-match season and a single 7/45 innings together still do not tell us what he will do on Australia's bouncy, low-turn pitches, where a spinner has to spin the ball in the air and batters play with patience. Kotian has no overseas Test data. Washington Sundar does - he has bowled in different conditions, and that is what makes him first choice. Saransh Jain is also in the picture. So if I am honest, Kotian's case is not for 'replacement', it is for 'backup'. And being backup is not bad - it is proof of India's spin depth, where even a third or fourth off-spinner has to argue for a place in the Test squad. But taking the story to 'he will be picked' is over-extrapolation, and in my profession that is the most common mistake. So my takeaway is clear, and I am filing it with a date. Before the Australia series squad announcement, my prediction: if Kotian is picked, he will be there as a third spinner or a reserve, not as the man replacing Washington Sundar. If he gets into the playing eleven and takes fewer than five wickets in the first two Tests, I will quote this article myself - provided he plays. That is the real test, and it comes in the next few months, not in the noise of the 7/45 headlines.

37 Wickets, 7 Matches and a 7/45: Why Tanush Kotian's Case for Australia Is Still Half-Coded

37 Wickets, 7 Matches and a 7/45: Why Tanush Kotian's Case for Australia Is Still Half-Coded

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