RTS-Snicko Accuracy Debate PAK vs WI Test-1 2026: Edge-Mark Row

The third umpire's screen had two pieces of information that disagreed. The hot-spot replay showed a clear mark on the outside edge of the bat as the ball passed. The Snicko trace — the audio waveform synchronised to the moment of bat-ball proximity — showed a flat line. No spike. The two pieces of evidence were saying opposite things, and a wicket call hung on which one was believed. The third umpire chose the mark over the silence. The bowling side celebrated. The batting captain stood at the non-striker's end with arms raised. The 2026 RTS accuracy row started there.

What Happened on the Delivery

The delivery in question came in the Day 3 session at Sabina Park. It was the 47th over of the Pakistan first innings, a back-of-a-length delivery angling across the right-handed batter, and the wicket-keeper appealed for caught behind on instinct. The on-field umpire said not out. The bowling side reviewed.

On replay, three things were checked: hot spot, Snicko, and ball trajectory. Hot spot showed a small but distinct mark on the outside edge. Snicko showed no audible spike at the relevant frame. The ball had passed close to the bat — close enough that a mark from glove or arm-guard contact was a possibility, but the location and timing were consistent with bat-edge contact.

The third umpire stayed with hot spot. The on-field decision was overturned. The batter walked.

Why Snicko Did Not Spike

The technology question is genuinely interesting. Snicko (also called UltraEdge or Real-Time Snicko) measures audio waveform around the bat-ball moment. It captures sound. Hot spot measures friction-generated heat through infrared cameras. It captures temperature change. The two technologies measure different physical phenomena. They usually agree because a real edge produces both sound and heat. They occasionally disagree.

Three plausible reasons for the spike absence in this case:

• Glancing contact: the edge was a feather contact, not a meaningful deflection, and the audio energy was below the system's detection threshold.
• Crowd noise mask: a stump-mic peak from another source masked the relevant frame.
• Bat-thumping coincidence: the bat tapping the pitch in the same moment created a competing waveform.

The broadcast engineer quoted post-match leaned toward the first explanation. The ICC's tech supplier line was that the Snicko system detected no audio above threshold and that hot spot was the deciding evidence. Both are honest answers. Neither is fully reassuring.

The Captain's View

Babar's post-match view, expressed carefully, was that he expected disagreement between the two technologies to be resolved in the batter's favour, on the basis that DRS exists to overturn obvious errors and a split signal does not meet that bar. That is one defensible reading of the protocol. It is not the protocol that exists.

Read the DRS complete guide for how the third umpire is supposed to weigh competing evidence. The short version: hot spot is decisive when the mark is unambiguous; Snicko is decisive when audio is clean; neither overrides the other when both are clear. The 2026 PAK-WI delivery was a case where one was clear and the other was silent. The protocol allows the third umpire to use the clear evidence. Babar's argument is that the silent evidence should weigh more.

The Engineer's Quote

A broadcast engineer involved with RTS calibration spoke to a journalist post-match on background. The engineer's point was technical: Snicko's sensitivity is calibrated against a reference noise floor at the start of each Test, and that reference can drift through a session as crowd noise and stump-mic ambient changes. A genuinely faint contact can fall under threshold at one venue and be detected at another. That calibration drift is not currently published.

The ICC's tech-supplier response — "the system performed to specification" — is true but does not address the calibration question. It is the kind of answer that puts a row to bed without solving the underlying issue. Read the Snicko vs UltraEdge explainer for the technical baseline.

The Comparable: 2026 LBW Snicko Debate

The other live row from this series is the umpire howler LBW Snicko debate — a different decision, same broad question. Snicko evidence has been challenged in two separate calls inside one Test series. That is unusual. It suggests either that the Sabina Park acoustic environment is particularly unfriendly to Snicko, or that the calibration tolerance has shifted, or that the protocol's edge cases are being stress-tested by sharper batting and bowling.

The Players-Association Position

FICA has, quietly, started asking for two things:

• Published calibration documentation per Test, with reference noise floor, peak detection threshold, and drift tolerance.
• A right of appeal — not to overturn the decision, but to log a formal post-match query when split signals decide a call.

Both are reasonable. Neither has been adopted.

Test	Snicko-disputed call count	Outcome
ENG vs PAK 2026 1st	1	Decision stood
AUS vs SA 2026 1st	0	—
PAK vs WI 2026 1st	2	Decisions stood
BD vs IRE 2026 1st	1	Decision overturned to not out

Two disputed calls in a single Test puts PAK-WI at the high end of the cycle so far. That is the data point that has driven the 2026 row.

What Happens at the Tech-Supplier Level

The ICC contracts the technology suppliers. The suppliers run the equipment. Calibration documents exist internally but are not currently shared with broadcasters or boards. That information asymmetry is the structural issue. Boards cannot challenge a decision's technological basis without access to the calibration data, and the suppliers will not publish without ICC mandate.

The most likely fix is a published calibration certificate per Test, with a redacted technical summary that does not reveal proprietary information. Several boards have asked for this. None has it.

What ICC Will Need To Decide

Two questions:

• Whether to publish a per-Test technical-calibration summary.
• Whether to formalise the third-umpire's reasoning template when hot spot and Snicko disagree.

The second is more achievable. A published reasoning template — "in cases of split signal, consider X, then Y, then Z" — would not change outcomes much, but it would change confidence in the outcomes.

What's Likely Next

Expect a quiet ICC working-group review on RTS calibration documentation. Expect the supplier to issue a confidence-restoring statement without committing to public calibration disclosure. Expect another split-signal call to surface within the next six Tests, by which point the conversation will have advanced.

The technology is good. The protocol around it can be better. The 2026 row at Sabina Park is the latest reason to make that protocol clearer. The wicket stands. The question stays open.