Two Days, 234 Runs and a Sourceless Scorecard: Miraz's Men on Day One in the UAE

At two in the morning a phone screen lights up with a number — 78.1. I am on the roof of a house in Barishal, leafing through an old notebook, and my fingers stop at seventy-eight and one. This is not a Test innings, not a one-day innings, and certainly not a T20 one. It is the first day of a two-day preparation match, and Bangladesh have been bowled out for 234 at a run rate of 2.99. The Barishal floodlights taught me that every match begins in the dark. So did this innings — a light switched on inside a dark scorecard, with one problem: nobody can yet say where the light came from.

Nineteen years of watching from the stands, of sitting in radio boxes and television commentary booths, have taught me one thing. A scorecard rarely lies, but the story behind it is very often unsourced. Today's innings is exactly that. One team batted. One bowler is said to have taken seven wickets. The opposition is 34 for 1. And then? No venue, no date, no series name, no umpires, no source for the original report at all. Every single information point carries the line: Source: None. In the entire history of cricket journalism I have seen only a handful of scorecards this incomplete.

The format has to be understood first, because it is the spine of everything else. In first-class structure, a two-day match is usually arranged for preparation, not for a result. Both sides get equal batting and bowling time, overs are shared out among new bowlers, and middle-order batters get long rehearsal hours at the crease. In such a game, who won and who lost is close to irrelevant. The relevant question is what the coaching staff found in the floodlit gaps. Reading 234 all out through ODI or T20 eyes would be a mistake. Patience, line, footwork against the new ball — those are the examinations here, not the numbers on the board.

The host side is the United Arab Emirates. In the language of cricket structure they are an ICC Associate member without Test status. Since gaining ODI status in 2026 they have built a different kind of cricket economy — in a country shaped by expatriate labour and professionals, the game is played largely by men of South Asian descent. They appeared in the first round of the 2026 T20 World Cup, and since 2026 their players have shared dressing rooms with world-class cricketers in franchise leagues such as ILT20. Without that context it is easy to file the UAE under 'weak opposition' and move on.

Bangladesh's red-ball identity sits elsewhere. In Test cricket we compete consistently at home on spin-friendly surfaces, but away wins are few enough to count on fingers. A preparation match on foreign soil therefore carries weight. Central contracts, squad rotation, the coaching staff's audit — all of it makes these two days a gateway to a longer red-ball assignment. In the language of a transfer window, the real story is not a star's price tag; it is the contract structure, the workload plan, and one new bowler's over-bank.

Now the number itself — 234 in 78.1 overs. Just under three runs an over. Through T20 eyes that is absurd; in red-ball terms it is normal tempo. Before the lacquer wears off, the new ball searches for swing and the batter spends the first hour defending. If a side is 210 for 4 after 70 overs, that is the pulse of a first-class innings. Panic about 'slow scoring' would only reveal a misunderstanding of the format. But something else is hidden here: the innings ended inside seventy-nine overs. In a two-day game you expect an innings to stretch to 110 or 120 overs. Collapsing at 78.1 means pressure built on the top order's foundation, and the middle order could not carry it.

The top three got in and none of them converted — this is the clearest, and most familiar, picture of the innings. Soumya Sarkar made 57 off 92 balls, a strike rate near 62, entirely acceptable for a red-ball top order. Sadman Islam made 46 off 95, a rate near 48, the natural patience of an opener. Naeem Hasan made 36 off 75. All three faced more than seventy-five balls, all three stopped short of fifty-plus, none reached a century. In football this is failing to finish after getting into the box; in cricket it is called start without conversion.

The middle of the order is quieter still. Mominul Haque made 33 off 63 — one of the most experienced Test batters in the side, yet confined today to a silent inner-ring role. Taijul Islam made 16 off 31; as a spinner he is not a frontline batter, but for a lower order even that matters.

The three names shouting loudest on this scorecard all sit in the middle and lower-middle order — Mushfiqur Rahim 4 off 14, Jaker Ali 8 off 33, Mehidy Hasan Miraz 8 off 15. Mushfiqur Rahim is a long-serving senior; a '4' beside his name means the day was not his. Jaker Ali consumed thirty-three balls for eight runs — in red-ball cricket that is not a crime, but if you are a wicketkeeper-batter tasked with setting the innings' tempo, it invites questions. Miraz, whose leadership the headline implies, fell for 8 himself. Khaled Ahmed made 10 off 23, Ebadot Hossain 9 off 27, Mushfiq Hasan 1 not out off 5.

Here we reach the number that placed the whole innings on one man's shoulders — seven wickets for a UAE bowler. Seven wickets in a red-ball innings means dominance. If one operator takes seven of ten, the others are simply holding the far end. But this is where my deepest doubt begins. The report names the bowler 'Mahbubul'. In lived reality, that name belongs to Bangladesh and the subcontinent, not to traditional Emirati naming. A first reading suggests a team attribution error. A second reading opens another possibility — what exactly is UAE cricket built from?

The UAE's domestic and national sides rest almost entirely on the children of South Asian expatriate families — Pakistani, Indian, Bangladeshi and Sri Lankan names are the rule there, not the exception. Muhammad Waseem, Junaid Siddique, Zahoor Khan, Basil Hameed, Alishan Sharafu, Aryan Lakra — one look at that list tells you a subcontinental name beside a UAE shirt is entirely ordinary. So leaping to 'the team was mislabelled' would be hasty. The better question is whether this name belongs to any known bowler in the UAE's domestic structure at all, or whether the report itself is an unfinished guess. Without a source, neither can be confirmed.

Bangladesh's bowling reply is comparatively clear. Ebadot Hossain broke through with the new ball — Luqman out at 24, caught by Ebadot himself. UAE's Bharat (16 not out) and Aftab (6 not out) then held firm, closing day one at 34 for 1 in eight overs. Trailing by 200 in a two-day game, the UAE are effectively in a first-innings practice phase. Ebadot's role deserves a word: he is Bangladesh's pace spearhead, and new-ball success in a warm-up is an encouraging signal for the series ahead. But in a two-day game, managing a fast bowler's over-bank is not a small matter.

This is where I bring in the Barishal lens. The Barishal floodlights taught me that every match begins in the dark — and the largest part of that dark is not on the field at all. It lives in budget meetings, bus-hire arithmetic, and muddy nets at small-town academies. The national middle order collapsed today, and its roots run deep into the domestic pipeline. Who bats at four? Has he scored six hundred runs across three straight first-class seasons, or was he picked on a two-match flash? To answer that you have to travel to Bogura, Khulna, Rajshahi, where regional selectors sometimes choose one boy out of three on the strength of a single innings.

One part of my press-box routine feels especially relevant today. In 2026, during my first paid radio commentary at Bangabandhu National Stadium, I misidentified Abahani's striker three times in ninety seconds and a rival fan page turned the audio into a viral humiliation. I did not defend myself online. I spent the next month re-listening to every tape, building a handwritten pronunciation and backstory index for two hundred players. Since then I have treated preparation as an ethical act, not a technical one. That lesson applies here — facing an unsourced scorecard, the bravest act is refusing to claim what we do not know.

Now to the blind spot collective memory so often skips. Cricket culture has an old disease: a warm-up result hardening into a verdict. A two-day rehearsal innings, in which both sides are experimenting, can fuse with the matches that follow and produce a false narrative — 'you see, that is where it began'. That 'where it began' story is the most dangerous of all, because it manufactures conviction without evidence. Soumya, Sadman and Naeem stopping near fifty is a conversion problem, but saying it was first seen in this match has no basis.

The greatest risk in this report is not on the field but in the information itself. Every data point says the source is unknown; there is no publication, no date, no venue. Any conclusion drawn here is a castle on sand. The worst offence in cricket analysis is not pretending to be wise; it is turning an unverified number into history. My nineteen years say the deepest harm of an incomplete scorecard is not its error — it is that people decide before it has even become true.

Yet inside that caution lies a real technical signal, worth watching even within the limits of one innings. If one bowler takes seven wickets in an innings, the question is not about his greatness — it is about what Bangladesh's lower-middle order did against that particular bowling type. Did he work with seam movement, or slow it down with carrom-ball spin? A two-day scorecard does not answer that. What it offers is a single number: seven. The number is lonely, unexplained, and precisely for that reason frightening.

I want to stand against my own first suspicion here. I thought a bowler named 'Mahbubul' being credited to the UAE meant a reporting error. But the history of cricket migration in the Emirates stops me. Where the children of expatriate families built the national structure itself, a subcontinental name cannot simply be equated with a mistake. Sourcelessness and error are two different offences, and this report shows evidence of the first, not the second. That distinction matters, or our doubt itself turns into superstition.

So what should we watch in the days ahead? First, whether Mushfiqur Rahim and the middle order regain runs in the next innings; if they fall cheaply across two innings, the warm-up warning becomes firm belief. Second, whether Soumya or Sadman reaches a century or a score above seventy, which would prove this innings an aberration. Third, whether 'Mahbubul' is genuinely a UAE bowler, verified against an authoritative scorecard. Fourth, whether this match precedes a Test or first-class series — the ICC Future Tours Programme or BCB schedule would tell us.

One thing I can say with certainty. The Barishal floodlights taught me that every match begins in the dark; but behind every scorecard runs a chain — groundstaff, regional selectors, bus drivers, scorers, reporters. The day one link in that chain breaks, the match may be floodlit but the story stays in the dark. Today's report is that broken link.

And I leave one question. If tomorrow's scorecard shows Soumya Sarkar making a century, Mushfiqur Rahim scoring seventy, and that UAE bowler taking two wickets — where does today's 234 all out and the seven-wicket haul go? To a corner of memory, or to a page of history? The answer depends on a scorecard that has not yet revealed its source.