Litton Das Is 50-50 for Mirpur, and the Ledger Says Ask About the Gloves

At eleven on Monday morning I stood behind the nets at the Sher-e-Bangla National Cricket Stadium in Mirpur and listened to one sound for ten minutes: spikes grinding on concrete, knees folding, the rise again. It was a keeping drill. I counted thirty-eight squats. Two nets away Litton Das was dragging a left-arm spinner towards long-on, and from the boundary rope the report writes itself — Litton is moving well. The ground was not empty; the microphones were not idle. What carried clearest that morning was the arithmetic of a man bending.

Cricbuzz reports that Litton remains doubtful for the first Test. The selection panel says it cannot declare him available or unavailable, and has called the situation 50-50. The call is being pushed "till the end". Team management has offered the more revealing line: 100% fitness is not really needed, minimum requirements will do. Litton himself is keen to play. All three statements pull in different directions, and all three can be true at once.

Then there is the date. The fitness test scheduled for October 24 was not taken. That detail carries more weight than anything said aloud. Skipping a scheduled objective benchmark is a different event from failing one: it means the medical staff judged that the test itself, and the load required to pass it, carried re-injury risk. The inflammation in the gluteal tendon has subsided and the pain has reduced, but stiffness, limited joint mobility and muscular weakness are still on the sheet. For a player in that condition, deferral is a decision, not an oversight.

The schedule around him: first Test at Mirpur from October 28, second at Sylhet from November 5, South Africa tour from November 15 with two Tests, three ODIs and three T20Is. There is no recovery window between the two Tests and none before departure. Litton missed the entire tri-nation ODI series against Zimbabwe and Afghanistan. He arrives at a five-day Test with no competitive cricket behind him — no first-class match, not even a 50-over game.

I keep the beat before I keep the opinion, and this beat has an old rule: nothing goes to print without a dated source log and a second document. Here I have the Cricbuzz report and no board medical bulletin. So I am publishing what can be counted — the dates, the quotes, the skipped test, the scene at the nets — and holding the causal claim until the second document arrives.

The misreading spreading fastest is that this is a batting question. Batting is the easier half. The question is how many times a man can bend behind the stumps across five days. Gluteal tendon inflammation sits around the hip joint, and keeping is the one job in cricket where the hip works on every ball. A net session is twenty minutes of batting with pauses built in; nobody forces a fast, deep squat. A Test keeper stands for 150 to 200 overs across five days, goes down repeatedly to spin, and at Mirpur — slow, low, turning — he spends most of that time up at the stumps. The same injury carries two very different loads.

This is how I have worked since 2026, when I sat behind the nets at Lord's with a hand clicker through India's tour and logged every delivery: 1,186 in practice, 1,412 in matches, spell by spell, bowler by bowler, dated. The lesson from that ledger has not changed. Practice load and match load do not belong on the same page. I went back to the nets this week to check what I remembered, and the nets said what they said thirty years ago: bat sound tells you nothing about whether a body can carry five days.

On the record: roughly 45 Tests, an average in the mid-30s, four hundreds, a strike rate near 60 — figures I am printing with the caveat that I could not verify them against a second source this week. The direction is not in doubt. Bangladesh bat at a team strike rate in the high 40s; Litton is one of the few who change the tempo of an innings. The argument for picking him rests on replacement quality, not on irreplaceability. A mid-30s average with a 60 strike rate is a real asset in that middle order; it is not a top-decile international keeper-batter profile, and inflating it is how bad risks get justified.

The conditions make the risk worse rather than better. Mirpur is the worst venue on this calendar for this specific injury. On a fast, bouncing surface the keeper stands back and the hip is spared; on a slow turner he stands up for 120-plus overs and squats on every ball that beats the bat. Bangladesh's home win route runs through spin, which is exactly the route that punishes a gluteal problem. Late-October humidity in Dhaka adds soft-tissue fatigue on top.

The replacement question is a batting question. Nurul Hasan and Jaker Ali are competent glovemen — the squad is not confirmed in front of me, so treat those names as inference — but their Test batting returns are materially below Litton's, a gap I would put at 15 to 20 runs of expected innings value. Bangladesh would be trading runs for durability, and in a two-match series with no runway, runs are the scarce resource.

The South Africa tour turns a one-match call into a six-week call. Two Tests, three ODIs, three T20Is from November 15, one body across three formats. A re-injury in Dhaka costs more than a Test. And the phrase in circulation — chronic workload — tells you the problem is cumulative rather than incident-specific. Cumulative load does not get treated by playing one more match.

The downside is asymmetric. A half-fit keeper who breaks down on day three leaves Bangladesh structurally short for the rest of that Test, and the failure mode is unlikely to be dramatic: it will be a gradual loss of mobility on days three to five, which is precisely when Mirpur Tests are decided. In a two-match series, going 0-1 down into Sylhet compresses everything, and the first Test is the heaviest match of the series, which is what makes it the least suitable place to take the gamble.

"100% fitness is not really needed" deserves a second reading. Treat it as a coaching-committee sentence rather than a medical clearance. It concedes he is short of full strength and reframes the question as meeting minimum requirements. That is a transfer of decision risk — from the medical staff to team management. In my experience, when "minimum requirements" enters the language, the honest answer has become politically inconvenient.

The outside reading has it backwards. Net clips are circulating — big shots, good timing — and being read as proof of readiness. One session, a few lofted drives, no scoreboard, no field, no pressure. The actions net practice tests least are the ones this injury attacks hardest: footwork against the short ball, running between the wickets, lateral movement for catches down leg. The reverse is also true, and it matters: the batting component is probably already acceptable, and the final assessment will hinge on a glovework drill.

My caution has limits and I will name them. Rain on the morning of October 28 would cut the keeper's load and make selection marginally safer. And if the medical staff are managing this as chronic load rather than acute injury, their plan may well be "play one Test, manage him through the tour" — except a keeper cannot be partially deployed, which is the crack in that plan.

One thing is being missed in the noise. A single hip is deciding the shape of Bangladesh's batting order. Blame for that does not sit with one selection. It is the structural truth of a mid-tier side with a thin experienced middle order and replacements drawn from the same generation.

So watch the morning of October 28, and watch the right drill. Not the batting. The keeping and fielding work, against spin, up at the stumps. If he goes down fifty times in ten minutes instead of thirty-eight and rises without changing expression, I will withdraw my doubt. And if he plays, the real verdict arrives with the South Africa squad announcement — that document will tell us whether Bangladesh mortgaged six weeks to win one home Test. I counted the deliveries, and the count told its own story. The next count comes from the middle.