From 124/0 to 346: The Innings That Wrote Bangladesh's Own Confession in Abu Dhabi

Not a wicket had fallen at 124. Then three fell inside four runs. In Test cricket such a number is not an accident; it is a statement. Watching the second morning of the Bangladesh-Afghanistan Test at Abu Dhabi's Sheikh Zayed Stadium from my home in Manchester, I had the sense that an innings had paused mid-sentence to confess something about itself. I thought I was watching a match, then I saw a confession.

Test cricket keeps its own clock — session-by-session attrition, a war of patience, and, somewhere inside it, sudden collapse. Someone gave that clock a shake in this match. Bangladesh were bowled out for 346 in the first innings. To travel from 124/0 to that number means runs arrived, but conviction did not. That gap, not the scoreline, is the real story.

The context is an uncomfortable tale in itself. This is Afghanistan's home Test, yet the venue is Abu Dhabi. There is no protection of playing on your own soil; a neutral ground forces them to carry the burden of being hosts. Bangladesh's position is no softer — out of familiar subcontinental conditions, onto a dry, slow, in-between surface, seven or eight flight-hours from home. The toss result is still unconfirmed, so the question of who carried how much pressure stays in the realm of estimation.

At stumps on Day One the board read 317/8. On the second morning it read 346. That intervening night was sleepless for Bangladesh, and here the first crack appears. The report says the last two wickets added 41 runs, and also that the score at stumps was 317/8. Do the arithmetic and the last two wickets account for 29, leaving a twelve-run discrepancy. Either it is a transcription error or the hurry of a wire-style bulletin — the outlet is unnamed, the byline is a single initial, and beneath it sits the phrase 'more details coming.' Every figure in this match is therefore data pending verification. Going to a firm conclusion before reconciling it against an authoritative ESPNcricinfo or Cricbuzz scorecard would, in my profession, amount to a professional offence.

What is reliable, though, tells the story. The 124-run opening stand was a platform; in Test cricket a stand that size means you have already taken the match's controls into your own hands. Then three wickets in four runs. In the long format, a cluster collapse and slow erosion are two different diseases. Slow erosion is ball, pitch, fatigue, clever field settings — normal accounting. A cluster collapse means a hinge: a bowling change, a set batter's dismissal, a sudden squeeze on the scoring rate. Bangladesh suffered the second, and that is not merely misfortune — it is a failure of communication inside the batting order.

This is where the journey from the training ground to the timeline becomes useful. A small habit in the nets — a trigger movement, a subtle change of grip — becomes 'loss of form' on social media the following week, and two matches later it enters the historical record under the word 'collapse.' I spent fourteen years on coaching staffs, the last four as an assistant, and there I learned that a team's true weakness is never born in a single day. The jump from 124/0 to 128/3 is the harvest of some older habit grown somewhere off the field.

When I stepped into the BPL commentary box in 2026, sitting beside Danny Morrison and Athar Ali Khan, one thing became clear — a middle-order collapse is never purely a matter of cricketing luck. It is a deficit of clarity between batters. Who absorbs the pressure, who rotates the strike, who chases the boundary — when that division of labour is unclear, one wicket invites the next, and then the next. Bangladesh got stuck in exactly that place.

The bowling arithmetic is more interesting than the batting collapse. Seven of Afghanistan's ten wickets went to pace — Mohammad Saleem Safi 4, Yamin Ahmadzai 3, Ismat Alam 2 — while the lone leg-spinner, Qais Ahmad, took just one. At a venue like Abu Dhabi, which is supposed to help spin as the match wears on, that dominance of seam is a wordless statement. Either the pitch was unusually seam-friendly on the first day, or Qais Ahmad was used outside a tactically sensible plan.

Naeem Hasan's unbeaten 35 from 67 balls is not a lower-order heroism; it is a silent indictment of the top order. If the only resistance from the tail comes off a spin-bowling all-rounder's bat, it means the top and middle order could not handle the surface's difficulty — yet the surface was not unplayable. Nobody survives 67 balls on an unplayable pitch.

The second disappointment hides here: Bangladesh's tail is long. That fact cost nothing in the first innings, because 346 was still a defensible score. But if Afghanistan bat well and build a hundred-run lead, that long tail becomes the rope on the gallows in the second innings. In Test cricket a side loses in two ways — by losing wickets, or by losing time. A weak tail invites risk in both.

So what is the orthodox reading? The conventional analyst will say Bangladesh squandered a fine start, and Afghanistan's pace exceeded even their own self-image. Neat, clean — and my suspicion is that it is not entirely true.

There is a reason to think the reverse. A neutral venue deletes Afghanistan's 'home advantage' variable from the equation altogether. Their seven pace wickets, then, came from no ground advantage; they came from pure quality and planning. That is the genuine signal about Afghan seam bowling — their resources travel beyond Kabul or Greater Noida, and they work on dry pitches abroad too. In time, this may earn value in their bilateral scheduling.

The second doubt concerns Qais Ahmad. The venue's reputation says spin will increasingly bite; yet by Day Two the leg-spinner had a single wicket. Two explanations are possible, with different consequences. One — the pitch is not yet taking spin, in which case the match changes shape on Days Three and Four and Afghanistan's pace-led plan falls hollow. Two — Bangladesh played Qais Ahmad defensively, which would be a plan worth praising. I lean toward the first possibility, because on a spin-friendly venue, a leg-spinner being under-bowled or under-rewarded in a Test usually speaks of conditions, not of batting skill.

This inference has a limit I want to state plainly: one innings, one pitch, one match. Drawing a settled verdict on conditions from so little is not my habit. I am marking tracking signals, not delivering a ruling.

One more thing must be said. The Abu Dhabi stands were sparsely filled, and the silence of empty seats is part of Test cricket. The empty stadium taught me that silence has a formation — sometimes it isolates the fast bowler further, sometimes it renders a batter's error more visible. In this match, the crack in Bangladesh's innings echoes back off the empty rows.

Three things I will watch over the coming days. First, Afghanistan's first innings — whether they pass 346, and by how much if they do. If they pass it, this collapse becomes historical; if not, it stays an ugly session. Second, Qais Ahmad's workload and turn on Days Three and Four — that will tell us whether the pace success was a property of the pitch or a gift from Bangladesh's shot selection. Third, Bangladesh's top order in the second innings. If another two or three wickets fall inside four runs, today's episode moves from 'a one-match accident' to 'a structural disease.'

346 is a number. But here the number is not the individual ceiling of batters — it is the product of a team's self-questioning. The journey from 124/0 to 346 is less a bowlers' tale than a batting order standing before a mirror. If the mirror comes back cracked in the next innings, then the matter is not only Abu Dhabi's pitch — the matter is the team's habit.