6/29 in Abu Dhabi: Hasan Mahmud's Hat-Trick, the 50th in Test History, and the Low Ball of the 83rd Over

I watched the ball of the 83rd over three times. Each time my eye went to the umpire first, not the ball. Where his body was at the bowler's end, how long he held his hand near the earpiece before the finger went up without hurry — those things tell me more than the scorecard does.

Afghanistan resumed on 211 for 4. I sat down with tea thinking the session might hold. It ended at 240 all out. Six wickets, twenty-nine runs, one session. In Test cricket the session is the most expensive currency there is, and this one was sold at the cheapest possible price.

My notebook has the session on a single line: Afghanistan's collapse did not come through spin, it came through pace — 211 for 4 to 240 all out, with nine of the ten wickets taken by two right-arm seamers.

Test hat-tricks are a rare species. This was the 50th in the history of the format — roughly a century and a half of cricket producing only fifty of them. That number matters, because in the subcontinental press the word hat-trick is used so casually that the rarity dissolves.

Bangladesh had two Test hat-tricks before this, and both belonged to spinners: Alok Kapali in 2026, Sohag Gazi in 2026. Hasan Mahmud is the first Bangladeshi fast bowler to take one. In a country where pace bowling has never been an inheritance, that line is not just a statistic; it is a hint of a cultural shift.

This innings also brought Hasan's 50th Test wicket, and the data says he is the fastest Bangladeshi fast bowler to reach it. The comparison is what gives it shape. Mashrafe Mortaza's entire Test career stopped at 78 wickets; Taskin Ahmed sits on 59. Fifty wickets is a complete milestone for a Bangladeshi seamer — moderate by global standards, large by national ones.

The match is Afghanistan's home series, but the ground is Abu Dhabi, a neutral venue. Afghanistan's home games now effectively mean a ground in the United Arab Emirates. That changes something large. A side that survives by curating spin-friendly surfaces to squeeze opponents loses that craft advantage on paper. In Abu Dhabi the Afghan spinners did not bite; the seamers took the bulk of the wickets.

And the ball kept low and came in — that single sentence is my biggest clue about the surface. A ball keeping low on day three means the pitch is starting to break, which is the first instalment of bad news for anyone batting fourth.

The morning was started by Ebadot Hossain. The cleanest delivery inside his 4 for 56 was the wicket of Ikram Alikhil — through the gate, the ball passing between bat and pad to hit the stumps. That ball, to me, is the turning point of the session. The hat-trick is a later story.

Now the three hat-trick balls, and they are three different things.

The first was back of a length, hit the surface, kept low and came in, and broke the stumps. The second took an edge, and Litton Das dived to his right at slip to take it — that catch is the most underrated moment of the sequence, because a few centimetres separated fingertip from grass. The third was lbw, and the umpire's decision survived a review, with ball-tracking showing the ball striking the top of off stump.

Three wickets in three different modes — bowled, caught, lbw. That is what moves a hat-trick out of the luck column and into the skill column. I do not trust a pattern until it survives three different angles. Here there were three separate angles, and all three held.

I re-watched the review on the third ball separately, because how the decision was produced is the lesson. The umpire gave it not out, Bangladesh reviewed, the projection showed the ball travelling in line with the stumps and below the height of them. The on-field call was overturned and the finger went up. There is no controversy here — this is one of those rare moments where the technology turned a decision in the right direction, and it only became possible because someone spent a review. Not flinching from using it at that point is what actually completed the hat-trick.

My real interest, though, is the number 83. The 83rd over means an old ball, one side nearly dead, a surface scarred by repeated impacts. There is no new-ball swing left, but reverse swing is possible. Hasan's hat-trick ball kept low and came in, which is not what that age of ball usually produces at the start of a session. This is inference, not evidence — but the tail wickets fell in the 83rd over, which is not the story of a new ball. It is the story of the back end of a session.

Now the other side of the story, the one that will be written about less.

Rahmat Shah made 105 — in his first Test as captain, and his fourth Test century, the second of them against Bangladesh. At 236 for 9 he was the last recognised batter standing. The hundred came through the collapse around him. It is a lone-hand innings, and a lone-hand innings means the burden of holding a team together sat on one shoulder.

That is my second note: a captain's century sitting beside a 106-run first-innings deficit is not coincidence, it is evidence of structural weakness — a good individual number covering a team's fracture.

Bangladesh made 346 in their first innings. Tanzid Hasan 83, Shadman Islam 67 — the openers built the spine, but nobody converted to three figures. Among the Afghan bowlers, Mohammad Saleem Safi took 4 for 82 and Yamin Ahmadzai 3 for 79 — seven wickets to seamers. Both attacks were seam-led, and that fact alone tells you what the pitch was.

Nine of ten wickets to pace. In a Test innings on Asian soil, that ratio is rare.

Now the part that gets buried under the hat-trick's light.

For years I have watched matches through the stump mic and the umpire's angle, and read the scorecard afterwards. In 2026 I sat in an empty stadium and transcribed 412 verbal instructions from the umpire across 90 minutes, and that day I learned that Silence for ninety minutes can explain more than a thousand replays. The same thing happened here.

Because the truth is that the hat-trick did not fell Afghanistan; Afghanistan had already fallen. The road from 211 for 4 to 240 was built by Ebadot, and the last three wickets were a footnote to an innings already broken. The hat-trick is not the sentence here, it is the full stop. The press will write it the other way round, because the story ends on the final three balls, and endings are what people remember.

So the narrative of a Bangladeshi pace resurgence being built today is not one I am buying yet. Sixty-four matches taught me that one spreadsheet is never enough. You cannot write a bowler's career from one innings — Hasan's career average, strike rate, home-versus-away splits, none of it is in this data. This is his fourth five-wicket haul, which is a signal of consistency, but between a signal and a proof there is a whole series of gap.

One more thing catches my eye. Nine of Bangladesh's ten wickets came from two seamers. That is a proof of strength and a proof of risk at the same time. If one of them breaks down, or the pitch offers no seam, who is the third option? That question has no answer in this match, and for any side it is the real examination.

Afghanistan's mirror is the same. They are rich in spin production, but still in debt on Test batting depth. Six wickets for 29 in one session is not an accident, it is a portrait of a young Test side's structure, where all the weight falls on one senior batter. A neutral venue gives them the travel advantage, but they pay for it by losing their own conditions.

I am also logging that the DRS worked correctly in this match, without controversy. The process was transparent before the finger went up, the tracking provided the proof, the decision stood. A system's credibility grows in small moments like this, not in big arguments.

So what is the real decision of this match? Bangladesh lead by 106, and the pitch is breaking. That is control, but not command. A hundred-run lead is valuable on a deteriorating surface, but what a pace-dependent attack does in a fourth innings is not yet something anyone can say.

— Root: Referee