The Smoke of Run Rate: Runs That Show Up on the Scoresheet But Don't Win Matches

It was nearly eleven at night in my Liverpool room, and I was reading a scorecard. One team had made 63 in the powerplay — five fours, three sixes, and a batsman whose body never once lost its rhythm on the crease. The other team had made 51 in the same match. The first number glitters more on the scoreboard. But I was reading the ball-by-ball log, and I knew the real story was buried in that second figure. My notebook has been doing this work since 2026 — telling me which runs push an innings forward, and which runs merely collect applause. We have made strike rate the measure of success in cricket. The auction bid, the broadcaster's graphic, the commentator's excitement — everything settles on a strike rate of 180. This pattern repeats in every major tournament. People ask who hit the fastest fifty, who cleared the ropes most often. Nobody asks which ball a batsman risked his wicket on, and which ball he left alone to save strength for the next over. When the fifteenth over is underway, six wickets are down, and a middle-order batsman is 22 off 20 holding the crease — that is the innings that decides the match. But it does not appear in any record book, because there is no 'explosive style' of winning a contest visible inside it. Over many years I have seen that the batsman who lets a scorching delivery go is the one who plays freely on the next ball. And the one who tries to hit every ball — if his performance does not rise above a strike rate of 70, the numbers will say the same. But the truth is that the batsman who does not come cheap, the one the broadcaster puts in his promos, is often on the crease at a strike rate of 170 — having never faced the toughest bowling of the match. He has already received all the batting luxuries his partner did not. This story returns again and again in the game's history. Sunil Gavaskar is remembered for his 36 centuries, but the 30 runs he made were a whole day's battle against a fast bowler. Sachin Tendulkar's innings of 241 is what people cite, where he built a partnership with the bowlers. These runs look small on the scoresheet, but the match result is decided by them. A year ago a franchise spent heavily on a young batsman whose strike rate was above 160. He smashed 65 off 40 in his first match. The crowd erupted. But in that innings he played 18 balls in which he could only take singles. In the last six overs his team was fighting for 40 runs. When he needed to open up, he had not filled that part of his notebook — the part I call 'how', not 'how much'. Another thing that is often missed — the bowling context. If a bowler bowls 12 overs in his first spell and concedes 40, his economy reads 3.33. That is a magnificent figure. But if five of those 12 overs came in a session when batsmen were set, and he conceded 30 in that period, then this magical 3.33 does not tell the real battle of the match where he should have been saved for the slog overs. James Anderson's economy rose slightly in the last five years of his career, but the quality of the overs in which he controlled the game does not show in any statistic. You judge a bowler not by his average, but by the over in which he shut the game down. Now the thing you will not find in any data sheet. In the 2026 World Cup semi-final, when Sachin Tendulkar was out for 85, I was sitting in that gallery of the ground from which the whole network is visible. India needed 30 off 19 balls. Yuvraj Singh and Suresh Raina were at the crease. Yuvraj played the innings that everyone will call an innings at a strike rate of 84. But I cannot forget that ball of the eleventh over where he dug out Brett Lee's yorker and hit it for four. His strike rate at that point was around 60. After the match people looked at the numbers and said, 'a good innings.' But the real value of that innings was that it kept India alive until the final over. Will you weigh that innings at a strike rate of 60? This is exactly where real analysis begins. There is an old rule of cricket — looking at any innings apart from its context is like opening an umbrella in the rainy season and waiting for the rain to fall. When I was playing for Lancashire's second team in 2026 and my back gave out, I opened my notebook for the first time that afternoon. On that first page I wrote — 'which over was the turning point of the match, and who did what in that over.' Thirty years later my method is the same. When a batsman makes 70 off 50, I first look at which five balls he left, and which ball he played with the intent of a six. The balls left alone are often the most valuable asset of that innings. What is happening in this tournament is a new chapter of the old story. Teams now count balls the way a company announces quarterly results. Every over has a target, every batsman's 'impact' is measured. But there is also a truth in tournament cricket that the pitch slows down in the semi-final and final, the ball gets old, and the pressure is of a kind no pre-match analysis can measure. In such matches a score of 140 can be heavy, and a score of 190 can be light. In the first World T20 in 2026, when India beat Pakistan in the final, nobody looked at the arithmetic of strike rate. That night Gautam Gambhir's 75 came off 54 balls — it looks slow. But without that innings India would not have reached the final. This is the mistake we keep making — viewing the result apart from the process. Another thing that troubles me — the number game. We identify players by their statistics, not by their story. A fast bowler who took 60 wickets in 40 matches is compared with a bowler who took 55 in 30. But nobody sees that the first bowler's 20 wickets came in innings when the opposition was already bowled out for 150, and the second bowler's 30 came in matches where he had to defend 200. Over many years I have watched 'character' fetch heavy bids at the auction table, and then the same player surrendering first when match pressure arrives. At the first auction in 2026 I was in that Mumbai ballroom where a player's price was fixed in 90 seconds. That day I wrote in my notebook — 'the price is not what the bid said, the price is what is paid under pressure.' I still write the same today. So in this phase of the tournament, when everyone is showering statistics, I want to ask one question. What is the value of the batsman who makes 25 off 10 and gets out, and what is the value of the batsman who makes 35 off 30 and stays not out? The first number looks bigger. The second wins matches. Until our notebook records this difference, we will keep reading the scoreboard instead of understanding cricket. And a scoreboard never wins a match — matches are won by the runs that nobody counts.