BD vs IRE Mirpur 2026 Light-Meter Stoppage Row Decoded

The light meter came out at 4:42 pm, the umpires conferred for two minutes, and 13 overs of cricket disappeared from the Mirpur Day 4 schedule. Bangladesh's wicket-keeper held up four fingers — four light-meter readings he disputed — and walked off shaking his head. Ireland's captain stood at mid-off with hands on hips, then trotted to square leg and asked the standing umpire, on stump-mic, whether the threshold was the same one used at Sylhet two weeks earlier. The umpire said yes. He was not wrong. He was also not the whole story.

What the Light Meter Actually Measures

The light meter used in Test cricket is calibrated to a baseline reading taken at the start of each session. The threshold for stopping play is not a fixed lux value — it is a relative drop from the session baseline, set by the standing umpires after consultation. The 2026 ICC playing conditions allow play to continue if the bowling side is using only spinners (low ball-velocity, less batsman risk), and pause when fast bowling is in operation below the threshold.

That nuance matters because Ireland was, at the moment of stoppage, bowling spin from one end and pace from the other. The umpires read the threshold against the pace operator. Spin would have been allowed. The captain's tactical question — could we change the bowling to keep playing? — was reasonable, but came after the readings had been logged.

Day 4 Sequence

The sequence on Day 4 went like this:

Time	Event	Light reading
4:38 pm	First light meter check	Above threshold
4:42 pm	Second check	At threshold
4:46 pm	Third check (after wicket)	Below threshold
4:48 pm	Umpires confer	—
4:52 pm	Play stopped	—
5:14 pm	Resumption attempt	Still below
5:48 pm	Day's play called	Still below

The 13 overs lost were the difference between a 5:48 pm scheduled close and a 4:52 pm actual close. Bangladesh, batting, would have preferred to continue — they were 28 runs ahead with 4 wickets remaining. Ireland, bowling, would have preferred to continue with the new ball still useful. Both wanted the same thing for opposite reasons. Neither got it.

Bangladesh's Position

Bangladesh's on-field protest was that the threshold reading taken at 4:42 pm appeared inconsistent with the reading at 4:38 pm — only four minutes earlier and with no apparent change in cloud cover. The keeper's "four fingers" gesture was a reference to the four readings he had counted. That count is correct. The disputed reading is the third one — taken after a wicket fell, which is standard practice — and the keeper's suggestion was that the reading was rushed.

The match referee subsequently confirmed all four readings were taken to spec. The match referee's confirmation is final under ICC playing conditions. Bangladesh's post-match note acknowledged the procedural correctness while questioning the threshold itself.

Ireland's "Play On" Plea

Ireland's captain made the case for spin-from-both-ends to keep play going. Under the 2026 playing conditions, that is a legitimate request — but only if both teams agree, and only if the umpires accept it. Bangladesh did not agree, on the basis that they were the batting side and the slip cordon would have been pulled in by light conditions regardless. The umpires accepted Bangladesh's position. That ended the request.

The Ireland captain's post-match comment was diplomatic. He said the light call was the umpires' to make. He did note that the threshold seems to drop earlier in Mirpur than at other Test venues, a comment that has been noted but not formally investigated.

The Threshold Question

There is an unresolved question about whether Mirpur's threshold has drifted. The reading is calibrated against the start-of-session baseline, but ambient conditions in Dhaka — pollution, haze, cloud — can produce a baseline that is already low at 9:30 am. If the baseline is low, the threshold (a relative drop) is also pegged low.

The fix, if there is one, is for the ICC to publish session-baseline figures so that bad-light calls can be audited externally. That has been requested, repeatedly, by broadcasters and player associations. It has not been adopted because of concern that auditing might politicise the call.

Comparable Cases This Cycle

Test	Date	Overs lost to light	Outcome
BD vs IRE 1st (Sylhet)	2026	4	Drawn
BD vs IRE 2nd (Mirpur)	2026	13	TBD
ENG vs PAK 2nd	2026	9	Drawn
AUS vs SA 1st	2026	7	Aus win

The Mirpur figure is the highest of the cycle so far. That is part of why the row has stuck. Read the Sylhet 1st Test recap for the comparison case.

What Players Want Changed

Three asks from current Test players, surveyed informally:

• Floodlight protocols at venues with the infrastructure (Mirpur has them, used inconsistently).
• Published session-baseline readings so calls can be audited.
• A captains' appeal mechanism — not to overrule, but to formally log a disagreement that the match referee reviews post-day.

The last of those is the most achievable. The ICC has discussed it in working groups. Nothing is on the agenda for ratification.

What ICC Will Need To Decide

Two questions:

• Whether to publish session-baseline figures for transparency.
• Whether to mandate floodlight use at venues equipped for it, instead of leaving the call to the umpires' threshold logic.

Floodlight mandate is the more impactful change. It would also change the financial picture for Test broadcast windows, which is why some Full Members are cautious about it. The Bangladesh vs Ireland ODI series does not face the same problem because ODI floodlight rules are clearer.

What's Likely Next

Expect Bangladesh's board to log a formal note (not a protest, a note) on the threshold question. Expect the ICC to publish a clarification on Mirpur's baseline calibration. Expect no rule change in 2026 but a working-group convening that may produce a 2027 amendment. The match referee's confirmation will stand. The 13 overs are gone.

Ireland deserved better light, Bangladesh deserved a faster ruling, and Test cricket deserved a transparent audit trail. Two of the three are achievable. The 2026 row at Mirpur is the latest reminder that the bad-light framework still has more work to do.