The Sylhet Dossier: Hasan Mahmud's 6/90, West Indies' 356, and the 'Dominance' File the Scorecard Never Opens

When West Indies resumed on the second morning at 235/4 — Aamir Jangoo on 111, Justin Greaves on 35 — the Sylhet International Cricket Stadium scoreboard told nobody that six wickets would fall before lunch and that a 400-plus platform would die at 356. By lunch West Indies were 322/8. That is four wickets for 87 runs in a single session: the arithmetic that turns a 'set batters' morning' into a 'bowlers' morning'. By stumps Bangladesh were 88/3, trailing by 268, and Hasan Mahmud had 6/90 — a fifth five-wicket haul in Test cricket, a new Bangladesh pace record, past Shahadat Hossain's four.

But let me walk you through the document before we touch the drama. Because the real story of this match is not in the wicket count. It is in one delivery — the second new ball — and in one regulation nobody quotes: the 200-run follow-on threshold.

The Sylhet weave: pitch, light and the new-ball economy

Sylhet's pitch has a known biology. The first hour or two offers seam movement; with cloud cover, swing sharpens; then the surface flattens into a good batting pitch. It is not a spin-turner — not by Day 2. The report in front of me is explicit that conditions were overcast and bowler-friendly. Which means the second morning was the window where bowlers would get the most help — and Bangladesh used that window fully.

Now place that inside the frame I always read first: a Test has two new balls, and the second one — usually around the 80th over — is the single biggest hinge in a match's economy. The first new ball arrives at the start of an innings, when batters are not set. The second arrives when batters are set, eyes are in, and the pitch has gone flat. That is the moment a fast bowler is summoned to break a set pair.

That is exactly what happened on Day 2. West Indies went from 235/4 to 322/8 to 356 all out. The centre of that collapse was the second new ball, which removed Jangoo and Chase on consecutive deliveries. That was not coincidence. It was a regulation producing a consequence.

Session one: four wickets for 87 — Bangladesh's session

Let me say it plainly: the first session of Day 2 belonged entirely to Bangladesh. 235/4 to 322/8 — four wickets for 87 runs. When you have two set batters and you are building toward 400, four wickets for 87 means you have lost your foundation.

This is where I see a familiar error in Test reporting — the error of ending the session with 'the bowlers won it' without asking what the batting did. The truth is that West Indies' middle order did not do the one job a Test middle order exists to do: supply a second anchor. Jangoo was on 133, but around him there was no batter who could play 150 balls and share the load.

The report shows three scores above fifty — Jangoo's 133, debutant Kevin Wickham's 61, and Greaves' 51. After that, Warrican's 27* is the largest score. The lower order fought; it fought and lost. This is the pattern I call 'the missing second anchor' — the thing that stops Test innings at 356 when the road to 450 was open.

The second new ball: the day's real hinge

Now to the delivery that decided the day. Jangoo had batted more than five hours for 133 off 212 balls. He was dismissed on the second new ball — caught. And off the very next ball, Chase went too. Those two deliveries are the actual story of this match.

A technical note here, because this is where selectors and analysts should both open a notebook. Jangoo's 133 contained 13 fours and 2 sixes — 64 runs in boundaries, roughly 48 per cent of his innings. That is high for Test cricket. It means he scored off punishable balls rather than purely accumulating. His strike rate, 133 off 212, is about 62.7 — normal to slightly brisk for a Test, implying intent without recklessness.

But his dismissal is a technical checkpoint. He fell not to spin, not to fatigue, but to movement and bounce off the hardest ball — the second new ball. That tells you there is a crack in his game when the ball is at its hardest. In the second innings, both the selectors and the opposing bowlers will dig at that crack.

Hasan Mahmud: 6/90 and the politics of a record

Now the man the report is built around. Hasan Mahmud — 6/90. This is not a containing return; it is a wicket-taking return. Fifteen runs per wicket within the innings means he was attacking, not strangling. West Indies still reached 356 — meaning Mahmud was the strike weapon, while Taskin Ahmed and Mehidy Hasan Miraz (two wickets each) supplied control and residual pressure.

Here is the number that actually matters: this is Mahmud's fifth five-wicket haul, a new Bangladesh pace record. It previously belonged to Shahadat Hossain, on four.

I am not raising that statistic because it is a record. I am raising it because it exposes a structural problem in Bangladesh's pace bowling. The historical ceiling has been low. Five-fors have clustered around a few rare careers, because surviving in this format has been the hardest part. A bowler who lasts three or four years in Tests climbs this list almost automatically. Mahmud's record is proof that he is now Bangladesh's premier Test pace spearhead on this surface — and the record itself is the evidence.

One more thing. His wickets came in two distinct modes. First, a new-ball cluster — Jangoo and Chase back-to-back. Second, a set-pair breaker with the older ball — Joseph. That is more valuable than a single new-ball burst, because it shows two modes: new-ball movement and old-ball bounce.

And the hat-trick? The report says he previously took a Test hat-trick against Afghanistan in the UAE — 'October' is mentioned, the year is not. That fact is unverified and pending confirmation. In this match he was denied a second hat-trick by an overturned lbw review. That is a genuine variance event — put it in the luck column, not the skill column.

Jangoo's 133: a century that writes its own rules

Aamir Jangoo is a wicketkeeper-batter, and his 133 was the spine of the innings. 212 balls, more than five hours, 13 fours, 2 sixes. I derived the boundary share above — about 48 per cent. That is the number that tells you how it was built.

If you ask me whether this was a flawless Test innings, my answer is no. It was a high-quality but not flawless innings. A 48 per cent boundary share alongside 212 balls describes a scorer who dominates loose bowling, but whose technique carries a checkpoint — movement and bounce against the hard ball.

Here I want to name something that is the default register of Indian cricket coverage and that I refuse: we narrate centuries through their statistics rather than their construction. '133 off 212' is milestone framing. The real questions are: when did those runs come, off which deliveries, in which partnerships. Jangoo's runs came when West Indies needed a foundation, and he was supplying it. But when the second new ball arrived, that foundation shook — and the whole innings shook with it.

Wickham and Greaves: runs from the new cap

This is the part I find most interesting, and the part that gets the least space. Two of West Indies' three big scores came from batters who were not the top order. Kevin Wickham — a debutant — made 61. Justin Greaves made 51, and he was the batter resuming on 35*, dismissed at 301/8.

Here is the conclusion I draw: West Indies' runs came from the lower-middle and the new cap, not from the top. That is a very large signal. When a debutant and a wicketkeeper-batter are a team's biggest contributors, it means the team's spine and the team's depth have inverted. The depth is saving it; the spine is breaking.

And here is where I repeat an old line — the room knew before the headline did. Those sitting in the Sylhet morning knew West Indies' top order was under pressure on this tour. The scorecard hid it at 235/4. The session exposed it at 322/8.

Bangladesh's innings: 22/2, then 88/3

Now the second innings. Bangladesh began and quickly slid to 22/2. Two early wickets. This is the same weak link that returns with this team every time — the top order.

The two dismissals came in different ways, and the difference matters. Nayeem Hasan edged a Seales delivery and was caught for five. That is a good-ball wicket; the bowler did the work. Tanzid Hasan was out 'attempting to hit Justin Greaves' for sixteen. That is a shot-selection error; the batter did the damage.

I file these two wickets in separate drawers, because their treatments differ. The first is not a question of technique — it is the product of good bowling. The second is not a question of technique — it is a question of discipline. In Test cricket, on Day 2, against a new ball, attempting to hit Greaves is a decision whose cost is paid by the whole innings.

But — and this 'but' matters — Bangladesh recovered from there. 22/2 to 88/3. Two partnerships: one of 29 runs, and one of 37* still at the crease. That is two set batters.

The follow-on rule: the arithmetic of 68

Here is the section no report writes, and the one I always write first. I read the clause first; the scandal was in the punctuation — there is no scandal here, but there is a regulation, and the regulation is this match's real power.

In a five-day Test the follow-on threshold is 200 runs. West Indies made 356. Subtract 200 — 156 remain. Bangladesh are 88/3. So Bangladesh need 68 more runs to avoid the follow-on, with seven wickets in hand.

That is a rule-derived inference, not stated in the report. And this is where I say: an auction is a filing with a deadline, not a rumour with volume. The same holds here — the match's real scoreboard is not the wickets, it is the threshold. 68 runs. Seven wickets. Two set batters. And two days (the third and fourth) that on this pitch should be the best batting days.

Which means Bangladesh's position looks better than 88/3 — but only slightly better. Because the surface that was improving for batting on Day 2 afternoon — a surface West Indies' own centurion implicitly rated as increasingly good for batting — will hand Bangladesh's remaining batters two easier days, before any late-Test deterioration.

Auditing the word 'dominance'

Now the section I am writing this whole piece for. The headline says the pacers restored West Indies' 'dominance' against Bangladesh. I have to audit that word, because it is not supported by the day's run flow.

Let us do the Day 2 ledger. West Indies scored 121 runs and lost six wickets. Bangladesh scored 88 and lost three. Put that in a session-adjusted ledger and it reads 'slightly ahead', not 'dominant'.

Yes, I will state the conventional view fairly in one sentence: West Indies batted first, made 356, and reduced Bangladesh to 88/3 — that is a good day. That is true. But a 'good day' and 'dominance' are not the same thing.

Here is my real objection. Going from 235/4 to 356 all out is a conversion failure. When you have two set batters and you have built a 400-plus platform, ending at 356 is a failure that should be written into the batting's criticism, not into the bowlers' praise. Both truths can coexist: Mahmud bowled superbly, and West Indies' middle order failed. The headline chose the first half and dropped the second.

And this is where I look at 'dominance' from another angle. In this Test, West Indies' collapse pattern — a set pair broken, then a cluster — is the signature of a side without a 'second anchor' in the middle order. That is not a session event; it is a structural event. If the structure holds, the next innings will look the same.

What next: the map for Day 3

On the third morning Bangladesh will resume on 88/3. Two set batters at the crease. 68 runs to avoid the follow-on. Seven wickets in hand. And a pitch getting better for batting.

My first question: when will West Indies take the second new ball, and can it deliver the same jolt Mahmud produced? Because this match's economy is built around the second new ball. Whichever side has the better bowler in that moment will pull the match its way.

My second question: will Bangladesh's top order repeat the same mistake on Day 3 — the attempt to hit Greaves, or the edge against Seales' movement? This team's illness is old, and its cure lies more in discipline than technique.

And my third question — perhaps the most important — is this: can West Indies' middle order find its 'second anchor' in the second innings? Because if it cannot, the result of this match will not be decided by the Sylhet pitch. It will be decided by the structure of West Indies' own batting — the same structure that turned 235/4 into 356.

The file does not shout; it waits for someone patient enough to read it. Sylhet's file still has three days left in it. And the page that names this Test's real winner — bowler, batter, or the regulation nobody quoted — has not yet been turned.