A Century Every Time Against Khulna: Al Amin Jr Again 102

Key points

The third day of the fourth round of the National Cricket League (NCL) produced four different stories at four venues, but the headlines belonged to one name: Mymensingh's off-spinning all-rounder Al Amin Jr, who struck a century against Khulna for the second successive season. Last season he made 102 not out against the same side; this time he was dismissed for 102. Same score, same opponent, and it is the fifth first-class hundred of his career — the fourth also came against Khulna.

Beneath the shine of the century, however, the match situation is very different. Mymensingh were made to follow on and finished day three on 315/9, only 135 runs ahead. Nine wickets are down, the last pair is at the crease, and Khulna need roughly 136 to win on the final day. This is a losing position, not a winning one — and the report's biggest weakness is that it never says so plainly.

The other three venues offered equally interesting cricket. Chattogram need 101 more against Sylhet with nine wickets in hand, having reached 126/1. Rajshahi lead Rangpur by 85. And the Barishal–Dhaka match, which made headlines before a ball was bowled, lost two full days to a wet outfield — not rain, but moisture in the ground. That is the most unusual fact of the entire round, and the report buries it in the second-to-last paragraph.

Al Amin's day: retired hurt on 101, returned, finished on 102

The sequence of Al Amin Jr's innings is the most fascinating part of the story. He had to retire hurt on 101 — meaning injury or physical discomfort forced him to leave the innings mid-way. Under the Laws of Cricket, a batter who retires hurt is permitted to resume the innings later, and that is exactly what Al Amin did. He returned to the crease after the eighth wicket fell. But the comeback lasted only two balls: he scored one run off two deliveries and was dismissed. 101 plus 1 makes 102.

That 102 became the final score of his innings and the figure in the headline. The arithmetic inside the article is fully sound here: 101 plus 1 equals 102, matching both the headline and the main paragraph.

The real story lies in the numbers. Last season, against Khulna, Al Amin made 102 not out. That was his fourth first-class century and it ended a six-season drought — six seasons without a single first-class hundred. This season, again against Khulna, came his fifth. The direct conclusion is that the last two first-class centuries of his career have come against the same opponent, and both times the score has been almost identical: 102 not out once, 102 the other time.

This is no ordinary coincidence. Scoring centuries against the same side in consecutive seasons is noteworthy in itself in first-class cricket; the near-identical scores make it rarer still. The article reports the pattern but does not quantify it — it never states that both of his last two first-class hundreds came against Khulna. The reader has to join the dots.

Al Amin is an off-spinning all-rounder for Mymensingh. In this match his contribution came with the bat, and in circumstances where the team was following on — under pressure, in the shadow of defeat. Runs scored in such a situation carry a different weight from an ordinary innings, although their effect on the result was limited.

The real picture: 315/9, only 135 ahead

Despite the headline century, Mymensingh's position needs to be understood clearly. The team had to follow on in the second innings, meaning it did not take a big lead in the first — rather, it trailed. At stumps on day three Mymensingh are 315/9, leading by 135. Both figures imply that Mymensingh were 180 runs behind Khulna on the first innings, since subtracting 135 from 315 leaves 180.

One fact worth noting is nowhere in the report: the reader cannot verify whether the follow-on was legitimate. The NCL is a four-day first-class competition, and in four-day matches the follow-on requires a first-innings lead of 150. A lead of 180 clears that threshold, so there was no rule violation — but the report never gives either first-innings total. That is the single biggest transparency gap in the piece: the most decisive event of the match rests on a number the article withholds.

Khulna's position is clear. Mymensingh lead by 135, so Khulna need 136 to win on the final day. Mymensingh have only one wicket left — the last pair stands between Khulna and the target. If that pair survives, the target grows; if it falls quickly, Khulna get a small chase. Khulna are plainly the favoured side, and the report never says so directly.

Besides Al Amin, Abdul Majid contributed 59 in Mymensingh's second innings. That is a solid effort in a total of 315, but the team needed more — reaching only 315 for nine even after following on is a weak position. The article itself concedes that Mymensingh were not comfortable, and that assessment is directly supported by the data given immediately before it: the follow-on and the 135-run lead. That is defensible news writing, not editorialising.

For Khulna, the report names Sheikh Parvez, an off-spinner, and mentions his fourth wicket, but gives no full bowling figures. That is another place where the report is stingy with numbers.

Al Amin's record: what the numbers say

Viewed purely as data, three things stand out.

First, the pattern of Al Amin's first-class career. His fourth century came after a six-season drought, and his fifth came the very next season. The longest dry spell of his career was ended by a century against Khulna, and the next century also came against the same team. This shows continuity of form, and also suggests that Khulna's bowling suits him for some reason.

Second, the similarity of the scores. 102 not out and 102. Producing almost identical scores against the same opponent across two seasons is a rare coincidence, and that is precisely why it became a headline.

Third, the return after retiring hurt. Leaving the innings on 101, coming back at the fall of the eighth wicket and being out within two balls suggests the team needed him but his body was not cooperating. Had he been fully fit, the score might have gone past 102 and Mymensingh's position might have been slightly better. That is inference, not fact — but the sequence of the innings points that way.

Chattogram–Sylhet: 101 needed, one wicket down

The second most absorbing contest is between Chattogram and Sylhet. Sylhet made exactly 218 in both innings — 218 in the first, 218 in the second. Identical totals across two innings are unusual in first-class cricket; it may well be true, but it is exactly the kind of figure that survives a transcription error, so it needs confirming against the scorecard.

Replying to Sylhet's 436, Chattogram made 210 in the first innings. That figure is not stated directly in the report but emerges from the target: Chattogram need 227 to win, meaning Sylhet's lead was 226. Subtracting 226 from 436 leaves 210. That means Chattogram trailed by eight runs on the first innings — a very narrow margin that shows how balanced this match is.

In the second innings Chattogram have reached 126/1 and need 101 more. This arithmetic is also clean: 227 minus 126 leaves 101. Opener Sadikur Rahman is unbeaten on 58 and Shah Paran is unbeaten on 51. Together they have put the team in a strong position. On the final day Chattogram need 101 with nine wickets in hand — clearly the favoured side, although first-class mornings can produce quick wickets, so the match cannot be written off entirely.

One important detail of Sylhet's second innings is ambiguous in the report. The article says Sylhet had 'lost seven wickets at 139'. That can be read two ways: the score was 139/7 (seven wickets down overall), or 139/9 (seven wickets fell today, on top of two already down). The two readings produce different scorecards.

One clue helps resolve the ambiguity: the report says Tofayel Ahmed, batting at number nine, made 47 to help the team past 200. If a number-nine batter is helping the side past 200, the likelier state is 139/7 rather than 139/9 — the innings was being rebuilt, not collapsing. But that is inference, not confirmation, and it must be checked against the scorecard.

Amit Hasan is the most tangled case in the whole report. He scored 34 and 20 in this match, but the report also says he was called up to the Bangladesh squad for the second Test against West Indies. The two facts are in tension: a squad member normally does not play NCL cricket. The likely explanations are that he was released to play, or that the call-up concerns a later date. As written, the two statements collide.

An even bigger gap is that Amit Hasan's team is never stated. His figures sit inside the Chattogram–Sylhet section but are attached to neither side. The reader cannot tell whether he made those runs for Chattogram or for Sylhet. This is the single largest under-specification of any player in the report.

There is another unnamed player: Chattogram's left-arm spinner, who took four wickets in each innings. That could mean eight or nine wickets in the match — the strongest individual bowling performance described in the report after Payel's five-for — and the player is anonymous. This may be an extraction defect, but until the scorecard confirms the name, the story remains incomplete.

One more thing the report omits: Chattogram are chasing their 'second win', but no points table is given. The phrase implies a table the reader cannot see.

Rajshahi–Rangpur: Payel's five-for, Rajshahi 85 ahead

In the match being played at Bogra, Rangpur made 256 in the first innings. Rajshahi's first innings was 25 runs short of that — 231, though the figure is not stated directly and emerges from the phrase '25 behind'.

In the second innings Rajshahi have reached 110/3, now 85 ahead. The arithmetic is again straightforward: 110 minus 25 leaves 85. On day three of a four-day match, a lead of 85 with three wickets down means Rajshahi have a chance to push the game forward, but the lead is not so large as to eliminate Rangpur.

The biggest individual story of this match belongs to Asaduzzaman Payel, who took five wickets for 64. The Rajshahi medium pacer is the standout bowling story of the round — and it is worth noting that he is the only bowler in the report with a five-for, because the bowling figures from the other matches are simply not given.

Rangpur's batting featured two half-centuries — opener Anik Sarkar made 75 and number five Iqbal Hossain made 70. Both were central to lifting the side to 256. Yet despite these figures, the report does not say how the Rangpur innings unfolded, when the wickets fell, or which batters Payel dismissed.

Barishal–Dhaka: two full days lost to a wet outfield

This is the most unusual and least discussed story of the round. The Barishal–Dhaka match, being played in Rajshahi city, lost two full days to a wet outfield — and the report emphasises that the cause was not rain but moisture in the ground. The distinction matters, because rain interruptions are routine, whereas an outfield unfit for play in dry weather raises questions about ground management.

When play finally began on day three, Barishal reached 266/8. Scoring that many in a single day suggests conditions were favourable for batting and the ground had been made playable. Wicketkeeper Mohammad Abdullah is unbeaten on 62 — a contribution from the lower order that was important for the side.

But the reader's most obvious question goes unanswered: after two lost days, is a result still possible? If yes, how much time remains and who must force the pace? If not, is the match effectively dead and are the points shared? The report answers none of this. It is a gap that forces the reader to do the arithmetic alone.

There is another confusion the report does not clear up: the Rajshahi–Rangpur match is being played at Bogra, while the Dhaka–Barishal match is being played in Rajshahi — the very city whose name is also that of a competing team. For readers tracking the league, this is confusing, and the report does not disambiguate.

The gap between headline and scoreline

The headline frames a personal milestone; the scoreline frames a defeat. Mymensingh were sent in again, they are 315/9, and the last pair alone stands between Khulna and a target of roughly 136. Khulna are the favoured side, and the article never says so plainly.

As for the talk of 'a chance for excitement on the final day', it is so soft as to be almost evasive. The honest sentence would be: 'Khulna need about 136 with a day to bat.' Rajshahi's position of 85 ahead with three wickets down should have been presented the same way — with clear numbers, not vague projections.

It would be unfair to say the report hides the situation. It mentions the follow-on, it concedes Mymensingh's discomfort, it gives the 135-run lead. The imbalance is one of emphasis, not concealment — the century was made the headline, the losing position was placed below it.

The prose shows clear signs of translation from Bangla — phrases like 'no ball was played', 'his wait ended' and 'a century whenever facing Khulna' carry the texture of translation. That is also why an ambiguity like '139 for seven wickets' may be an artefact of translation rather than a reporting error.

What the report does not contain

Anyone trying to reconstruct a scorecard from this article cannot do so. The gaps are clear:

First, the first-innings totals for Mymensingh, Khulna and Chattogram are all missing. All three are derivable, but none is stated.

Second, bowling figures are almost absent. Only Payel's 5/64 and Parvez's 'fourth wicket' are mentioned. No other bowler's figures appear.

Third, no points table or standings are given, despite the reference to Chattogram's 'second win'.

Fourth, there is not a single quote from any player, coach or official; no BCB or scorer attribution.

Fifth, toss information is missing for three of the four matches.

Sixth, there is no mention of the points system or of who decides on the follow-on.

Seventh, and most importantly, the date. 'Third day', 'today', 'last season' — no absolute date anywhere. The only external anchors are the second Test against West Indies and the NCL round. The piece cannot be independently dated from its own text.

What to check next

Four scorecards should be pulled and confirmed, in this order:

1. Khulna's and Mymensingh's first-innings totals, and the 180-run deficit.
2. The name of Chattogram's left-arm spinner and his match figures.
3. Amit Hasan's team, and his availability relative to the Test squad.
4. Sylhet's twin 218s, and the 139 state (139/7 or 139/9).
5. Chattogram's first innings of 210.
6. The article's date and the NCL round.

If items 1 and 5 confirm, the piece's numerical reliability is high across the board — the arithmetic checks out one by one in all four matches. The only remaining risk would then be the under-specified Chattogram–Sylhet section.

Conclusion

The biggest headline of this round is a century, but the biggest story is that the team which produced it is standing at the edge of defeat. Al Amin Jr struck a century against Khulna for the second successive season, retired hurt on 101 and returned to reach 102 — outstanding on a personal level. But Mymensingh are 315/9, only 135 ahead, and Khulna need about 136 on the final day. The headline and the scoreline are both individually correct; the difference is that the report placed the headline on top and the scoreline beneath it.

Chattogram need 101 with nine wickets in hand; Rajshahi lead by 85; and Barishal–Dhaka, having lost two full days to a wet outfield, is searching for a result the report does not define. That is the real picture of this four-match round: numerically accurate, but incomplete in transparency.