Sylhet Day 2: Hasan Mahmud's six-for, the seam of the second new ball, and the unfinished ledger of 'dominance'

Sylhet International Cricket Stadium, Day 2 of 5, the fifth day still ahead. West Indies bowled out for 356, Bangladesh 88/3 at stumps. On paper this is an ordinary match report. But when I line up the three columns of the scorecard — over, run, wicket — one by one, the story isn't in the headline. It's in the margin.

I was sitting behind the scorer's table — that's been the habit since 2026, closer to the scorebook than the press box. My notebook has a different entry for that day. The second new ball arrived, Amir Jangoo had been at the crease for more than five hours — 212 balls, 133 runs, thirteen fours, two sixes. And then one ball changed everything. Jangoo out, caught. The very next ball, Roston Chase out too. The scorebook calls it two wickets, but the journey from 235/4 to 322/8 was settled in that one hour of the morning when the ball was hardest and the batters were at their most set. At the moment Jangoo fell, the second layer of the crowd noise was silence — and that silence wasn't coming from Bangladesh's dressing room, it was coming from West Indies' middle order. I went back to the tape to hear what the crowd missed.

This is a Test match. Two innings are still in progress on both sides, no declaration or follow-on decision has yet been forced. The pitch behaviour on this day was clear: seam movement and overcast-assisted swing with the new ball for the first hour or two, then a surface that flattens into a good batting pitch. On Day 2 this was not a spin-turner. The ball Hasan Mahmud used to dismiss Jangoo had both 'movement and bounce' — that is not just a wicket in the scorebook, it is a reading of the pitch.

The problem is this: who won the toss, who won the first Test, what the series score is, and whether this Test carries World Test Championship points — none of it is recorded in the Stage-1 source. The source is a single match report with no outlet name, no journalist byline, no dateline. The wicket-takers' sum (Mahmud 6 + Taskin 2 + Mehidy 2 = 10) is internally consistent, and that is its greatest credibility. I will not go past that into series-level claims, because what isn't in the record doesn't go in my column.

Now the real arithmetic. Split Day 2 into three sessions. Morning: West Indies 235/4 to 322/8 — four wickets, 87 runs. That session was decisively Bangladesh's. Afternoon: 322/8 to 356 all out — two wickets, 34 runs. Evening: Bangladesh 22/2, then 88/3, with a 29-run stand and a 37* stand after two early wickets.

Add those three figures together and the day's real face emerges: West Indies lost six wickets for 121 runs in their innings and took three Bangladesh wickets for 88. The session-adjusted ledger says 'slightly ahead', not 'dominant'. Whatever the headline says.

The second new ball is the decisive variable in this match's economy. Mahmud's post-new-ball spell — Jangoo, then Chase off the very next ball — is the only passage in the day where the bowling side systematically broke a set partnership with the harder ball. Jangoo and Chase falling to consecutive deliveries is structure more than coincidence: seam of the new ball, footwork of a set batter, catch to the wicketkeeper.

Mahmud's six wickets came in two distinct modes, and that is what separates him from a single-mode fast bowler. The first mode — a new-ball cluster, Jangoo and Chase back-to-back. The second mode — breaking a set pair with the older ball, Joseph. Taking wickets with the new ball is expected of a seamer; breaking a settled stand with the old ball is skill. 6/90 is a wicket-taking return, not a containing one — about 15 runs per wicket within the innings, with West Indies still reaching 356. He was the strike weapon; Taskin and Mehidy (two each) supplied control and the residual pressure.

The fifth five-for here became a record — the most five-wicket hauls by a Bangladesh fast bowler, moving past Shahadat Hossain, who had previously shared the mark on four. That statistic by itself states Bangladesh's pace-bowling ceiling: five-fors here have clustered around one rare career, not a generation. Mahmud's name now sits at the top of that list, and it should be a structural outlier for him — his predecessors rarely survived long enough in the format to accumulate the count.

One more thing the scorebook doesn't show: the overturned lbw review that denied Mahmud a hat-trick. That is a genuine variance event — the umpire's call, the review, the bowler's missed moment. Mahmud had earlier taken a Test hat-trick against Afghanistan in the UAE; the report gives the month as 'October', not the year. I have kept that claim in my pocket until the record agrees — the date is pending verification, so I keep it here as a sourcing note, not as a conclusion.

Now West Indies' collapse. From 235/4 to 356 all out — the last six wickets for 121 runs. Jangoo and Greaves were set at the crease. For a side that had built a 400-plus platform to fold for 356 is a conversion failure, not a pitch failure.

And look where the runs came from: 133 from Jangoo (wicketkeeper-batter), 61 from Kevin Wickham (on debut), 51 from Greaves, and 27* from Warrican. Three scores above fifty, and they came from the lower-middle and the new cap — not the top order. This is the pattern of a side whose middle order lacks a 'second anchor': one partnership breaks, and a cluster of wickets follows. The Jangoo-Greaves stand broke, then a cluster.

Jangoo's 133 is a high-quality Test innings, but not a flawless one. 133 off 212 balls — a strike rate of roughly 62.7, normal-to-slightly-brisk for a Test century. So there was intent, not recklessness. But look at the boundary share: thirteen fours and two sixes, i.e. 64 runs, about 48 percent of the 133. That is high for Test cricket — roughly half the innings came from boundaries, meaning the scoring pattern was built on punishing loose balls rather than pure accumulation. Such a batter owns the loose ball, and is a question mark against the hard one. His dismissal was a catch off the second new ball — not to spin, not to fatigue, but at the moment the ball was hardest. That is a technical checkpoint selectors and analysts will track in the second innings.

Bangladesh's evening was mixed, and the nature of the two wickets is different. Nayeem Hasan, on five, edged a Seales delivery to be caught — a good-ball wicket, credit to the bowler. Tanzid Hasan, on sixteen, was out 'attempting to hit Justin Greaves' — a shot-selection error in a Test. One good-ball wicket and one shot-selection error, both inside the same 22/2. So Bangladesh's problem is discipline, not technique — at least in this small sample, and I won't push it beyond two dismissals, but the signal is recorded where it should be.

After that came a 29-run stand and a 37* stand, and 88/3 at stumps. There is a subtlety here that doesn't make the headline: 88/3 slightly understates Bangladesh's position, but only slightly. Two set batters are at the crease, and the surface — which West Indies' own centurion implicitly rated as increasingly good for batting — will get easier as the days pass. On the other hand, 22/2 in the toughest batting window shows the top order is still the weak link.

The follow-on arithmetic is straightforward too, and it is rule-derived rather than stated in the report: the standard five-day threshold is 200 runs, so subtract 200 from 356, and Bangladesh need to reach 156. They are on 88 with seven wickets in hand — 68 more needed. High confidence on the rule, medium on its tactical salience for this captain, because plenty of the day remains and the follow-on call will also rest on the heat and humidity of Days 3 and 4. Sylhet's humidity and monsoon-adjacent rain risk could shorten this Test — but there is no weather information in Stage-1, so any rain-based forecast is speculation, and I leave it there.

Now the part for which I opened the whole ledger. The headline says the fast bowlers restored West Indies' 'dominance'. I laid the day's run flow out session by session, and it does not show dominance. West Indies lost six wickets for 121 runs in the day — that is a collapse, not a restoration. They took three Bangladesh wickets for 88, two of them inside the first 22 runs — a good start, but not enough for the word 'dominance' when the other side is sitting with seven wickets and is only 68 runs from the follow-on.

Here I have to resist an old habit: writing gently about cricket that gets little coverage. Low coverage does not mean no questions. Ask the same hard questions of Bangladesh's pace record as you would of a major board — Mahmud's fifth five-for is a structural outlier, and an outlier does not make a generation. Ask the same of West Indies' middle order: after one anchor, who is the second anchor? The day's numbers say: nobody.

The thing most easily missed is that the pitch was batting better on Day 2 afternoon than on Day 2 morning. The direct implication is that Bangladesh's remaining batters — who will play the two easiest batting days (Days 3 and 4) — will walk out with the highest probability of avoiding the follow-on. This is my reading, at medium confidence, and I put it down as an open possibility, not a conclusion.

I found the story in the margin, not the headline. The headline says dominance was restored; the ledger says a slight edge, and that too after a day in which West Indies lost their own innings. That one hour of the second new ball is the real story — it dragged West Indies from 400 to 356, and then the same weapon stalled Bangladesh's evening at 22/2. This isn't dominance. It's balance.

The forward signal lies in the third morning. If Bangladesh's set pair get through the first hour — when the new ball will again find seam — the 68-run mountain gets smaller, and the question swings back to West Indies' middle order in the second innings. If Mahmud takes one more in that first hour, Sylhet becomes another day-by-day ledger in which the word 'dominance' stays unfinished. What I will watch most closely is Jangoo's second innings — her footwork against the second new ball, and whether she falls the same way. A century built on 48 percent boundaries will answer the same question next time.

How this was checked: the figures come from a single match report with no outlet, byline or dateline — medium-low reliability. The wicket-takers' sum (6+2+2=10) was checked internally. Jangoo's strike rate (133÷212×100≈62.7) and boundary share ((13×4+2×6)÷133≈48%) are derived calculations, not in the report. The 156-run follow-on threshold is rule-derived, not in the report. The hat-trick date and toss/series status are unconfirmed — the related claims are deliberately withheld.