India Rested Mohammed Siraj. The Numbers Say That Was The Problem
Every fast bowler in the world would take a two-month break gladly. Mohammed Siraj is the rare case where that break became the problem, not the fix - and the numbers from before and after tell you exactly how much it cost him.

Context matters here. Siraj bowled 1,113 deliveries - 185.3 overs - across five Tests in England last year, the heaviest workload of anyone on either side; only Chris Woakes came remotely close at 181 overs, and Siraj still returned 12 more wickets than him for a series-best 23. By any conventional read, a bowler carrying that load deserved exactly the kind of extended recovery he eventually got. Following India's lone Test against Afghanistan on June 8, Siraj didn't play competitive cricket again until a warm-up fixture in Colombo on August 7: a full two months, the longest break of his ten-year career.
Why the Break Backfired for Mohammed Siraj
The problem wasn't fitness. Siraj kept working out and bowled occasionally through the layoff. The problem was that gym work and casual bowling can't replicate what match intensity does to a fast bowler's rhythm - and rhythm, for Siraj specifically, isn't a nice-to-have. It's the entire mechanism. He described himself as "purely a rhythm bowler," someone who can't generate pace without his run-up locking into a consistent, uninterrupted stride pattern.
The Sri Lanka Tests exposed exactly what happens when that pattern breaks. Shubman Gill used him for just nine overs per innings in the Galle Test - the least of any of India's five frontline bowlers - and Siraj finished the two-Test series with only 44 overs total, 14.3 fewer than second pacer Prasidh Krishna. His pace dropped into the late 120s and early 130s kmph, a significant fall from a bowler who'd clocked a 143kmph yorker at the Oval less than a year earlier.
Mohammed Siraj's Duleep Trophy Numbers Tell the Recovery Story
Selectors sent Siraj into the Duleep Trophy final in Chennai specifically to rebuild what the layoff had taken away, and the first innings showed how far he still had to travel: 25 overs, 145 runs conceded, no wickets, an economy rate of 5.60 that reflected genuine struggle rather than bad luck. But rather than treat that innings as a setback to move past quickly, Siraj pushed for more of exactly what wasn't working yet - bowling long spells of 10 and 11 overs, including a seven-over burst straight through with the new ball in the second innings, even once the match was already decided.
By the second innings, the speed gun had climbed back into the high 130s kmph. The run-up, by his own account, had returned to its natural shape.
What the Numbers Confirm About How He's Built
Strip away the quotes and the pattern is purely mechanical: less bowling correlates directly with lower pace and worse control for Siraj, in a way that doesn't hold for most fast bowlers his age. Mohammed Shami, by contrast, didn't need spells longer than four overs in the same match to look sharp - a reminder that workload management isn't universal, and that the modern instinct to protect fast bowlers with rest can actively undercut a bowler whose effectiveness is tied to volume, not recovery.
Siraj's own read on it, offered without much elaboration needed: "That's just how my body works - the more overs I bowl, the better I get." It's a simple enough sentence, but paired with the numbers - 44 overs in Sri Lanka producing a bowler firing in the 120s, versus 1,113 deliveries in England producing a series-best 23 wickets - it reads less like a preference and more like a documented fact about how his body operates under load.
The Adjustment Going Forward
None of this makes Siraj fragile. It makes him an outlier in exactly the direction modern fast-bowling management doesn't usually plan for. Shami's on-field advice to him between innings - get back to basics, let rhythm dictate line and length - worked, but the deeper lesson belongs to India's team management as much as to Siraj: for this particular bowler, extended rest isn't automatically protective. Sometimes it's the thing he needs protecting from.


Click it and Unblock the Notifications
