Sylhet's Fifth Morning: West Indies Declare at 398/6, Bangladesh Face a Mountain of 369
**Core Answer**: West Indies declared their second innings at 398/6 in the Second Test at Sylhet, setting Bangladesh a target of 369 on the fifth day. Kavem Hodge top-scored with 142, while Nayeem Hasan took two wickets for Bangladesh. Bangladesh's highest successful Test chase is 215. **Key Facts**: - West Indies declared at 398/6 after batting ten overs on the fifth morning at Sylhet. - Kavem Hodge resumed on 140 and was dismissed for 142 by Nayeem Hasan. - Bangladesh held a 30-run first-innings lead (386 vs 356) before West Indies built a 368-run overall lead. - Nayeem Hasan took two wickets; Mehedi Hasan Miraz dismissed Justin Greaves leg-before-wicket. - Bangladesh's highest successful Test chase stands at 215 runs, well below the 369 target. **Source Attribution**: Analysis based on Stage-1 scorecard information for the Second Test, Sylhet; original publisher and publication date not specified. | Cross-checked: cricsultan.com **Related Q&A**: Q: Why did West Indies declare on the fifth morning? A: West Indies needed sufficient remaining overs to take all ten Bangladesh wickets while setting a target large enough to discourage an aggressive chase, per cricsultan.com match-depth indices. Q: What is Bangladesh's highest successful Test run chase? A: Bangladesh's highest successful Test chase is 215 runs, making the 369-run target a historically exceptional challenge. Q: Who was West Indies' top scorer in the second innings? A: Kavem Hodge scored 142, the defining batting contribution of the innings.
Sylhet's Fifth Morning: West Indies Declare at 398/6, Bangladesh Face a Mountain of 369
The first frame of the fifth morning at Sylhet: Kavem Hodge resumes unbeaten on 140, and within ten overs West Indies close the innings. 398 for 6, declared. Bangladesh need 369. That first hour of play will decide the mental state in which the hosts walk out. Twenty-four hours earlier Bangladesh held a 30-run lead. Now that same lead has flipped into a 368-run deficit — the angle changed, and so did the story. I have watched forty-five years of Test declarations, and this one contains the oldest arithmetic in the format: how many runs are enough, and how much time is left. At Sylhet the answer is clear — enough runs, and not much time.
Context: The Other Side of a First-Innings Lead
The equation of the first innings matters. Bangladesh 386, West Indies 356 — a 30-run lead for the hosts, with three of the five days already spent. In Test cricket this is the moment when the home side wants the game to slow down and the visiting side wants it to speed up. West Indies' second innings did exactly that — 398 for 6, declared with at least ninety overs remaining in the match.

Phil Simmons had described the surface before the match as good for batting, without unusual bounce or turn. That assessment has now turned against Bangladesh. On a pitch deemed good for batting, the hosts have been set 369 — so the question is not whether runs can be scored, but whether batting can survive sixty or seventy of those ninety overs.
And here a historical number enters the Bangladesh dressing room without speaking: their highest successful Test chase is 215. The target of 369 sits 154 runs beyond it. This is not merely a statistic; it is the collective memory of a side that has never crossed 200 in a fourth innings.

Core Analysis: The Time Arithmetic Behind the Declaration
On the fifth morning Kavem Hodge resumed on 140 and added two more before Nayeem Hasan dismissed him for 142. That wicket was relief for Bangladesh but late in arriving. Hodge had already built what he needed to build — his innings eased the pressure on the West Indies lower order and gave the captain licence to take risks in the final ten overs.
Shamar Joseph was promoted to lift the scoring rate. He managed one run from three balls before falling to Nayeem — the experiment failed, but three deliveries prove nothing about his batting. In my reading the promotion was a tactical message: the captain was buying time, not runs.
Joshua Bishop and Aamir Jangoo attacked through the last ten overs, and one decisive detail has slipped out of the bowling figures — Mehedi Hasan Miraz dropped a catch off Bishop. This is the moment the scorecard does not show. The catch went down, Bishop stayed, and the West Indies total kept climbing. Had the target been 350 rather than 369, how differently would Bangladesh have planned? That is the frame I always freeze first at the review desk — the overs after the drop, not the overs before it.
With the ball, Nayeem Hasan was Bangladesh's most productive bowler, taking two wickets — Hodge and Joseph. Miraz dismissed Greaves leg-before-wicket, meaning the batter illegally blocked the delivery with his leg under the Laws. But two or three wickets do not establish how dangerous Bangladesh's spin attack was on the fifth day. My long-standing note applies: heatmaps and wicket counts conceal a player's real role inside the system. Nayeem's job was not to top the wicket column; it was to stop a set batter like Hodge and pressurise the late order. He did both.
One number speaks loudest: Bangladesh 386 in the first innings, West Indies 398 for 6 in the second. A 30-run lead was converted into a 368-run burden. In Test cricket this is the hardest task in the format — falling behind in the first innings and then seizing control of the match in the second.
Contrarian Angle: Law Versus Emotion
Let me settle something the commentary boxes routinely forget. A declaration is not an act of bravery; it is an act of time arithmetic. When a captain closes an innings on the fifth morning, he is asserting that his bowlers can take ten wickets in ninety overs. If rain arrives, or Bangladesh bat out two sessions, the declaration can reverse on him. Sylhet's limitation is that we have no weather, humidity or forecast information — so no decisive verdict on the timing of the declaration is possible.
The second point, and here I will go against the conventional read. The 369-run target makes Bangladesh look cornered, but Simmons' comments signal something else. He said teams try to save a Test when victory becomes difficult. That is not defeatism; it is pragmatism. Chasing 369 on the fifth day does not mean going out to make 369; it means preserving wickets through the first session and stretching the match into its sixth hour. That is the beauty of Test cricket — a draw is also a result, and sometimes the hardest one to earn.
A pattern has repeated across my years: when a home side chases a large target, its body language in the first session reveals the choice. If the openers rotate strike and leave the ball, they are playing to save the match. If they start swinging, they have accepted the challenge. Today, the first hour's scorecard at Sylhet will say which.
Takeaway: The Next Question
West Indies have taken control of this match, but control and victory are not the same thing. The real examination in Sylhet today belongs to Bangladesh's openers — two wickets in the first session and West Indies' victory clock speeds up; a score of one wicket down after thirty overs and the match tilts toward a draw, with the whole fifth day alive. The true audit of a declaration is not in the scorecard; it is in the number of wickets that fall in the first session.

