Fourth Slip, Three Jugglings and a Trap: How Sri Lanka Closed the Net on Babar Azam in Lahore

You did not need a replay to understand that ball at the Gaddafi Stadium. A delivery climbing to shoulder height, a fielder stationed at fourth slip, and Babar Azam's bat in the air. The board read 14/2, the fourth over was on, and the chase was 326. The ball spilled out of the hands three times; the fourth attempt stuck. The commentary box called it 'sensational' and closed the file. My notebook was asking something else: why was there a fourth slip in the fourth over of a 326 chase?

The whiteboard remembers what the crowd forgets. The crowd saw a catch. The whiteboard saw a field setting that tells you Sri Lanka's captaincy had planned for a wicket in that over, not for containment — and the wicket had a name on it: Babar Azam.

Context: A final in Lahore, and an incomplete report

This is a tri-series final — Pakistan, Sri Lanka, England, 50-over format, staged at Pakistan's own Gaddafi Stadium in Lahore. Not an ICC global event, not a league; the decider of a three-team series. The format's rules are fixed: two new balls, only two fielders outside the circle for the first ten overs, eight inside.

The report stops at the fourth over of the second innings. The picture to that point: Sri Lanka posted 325–326, built on Kamindu Mendis's 131 off 128 and Pavan Rathnayake's 77 off 65, with a 146-run third-wicket stand between them. Pakistan's chase had collapsed to 14/2 — two wickets inside the first 22 balls.

What happened next, the report does not record. The result of the final is absent. There is no match date, no toss, no weather, no dew, no clarity on DLS applicability. Without those conditions I will not assert an outcome — what I can do is dissect the state of the scoreboard at that moment, because that state is what tells you how heavy the catch was.

A 326 chase means 6.52 runs per over from the first ball. Being 14/2 after 3.4 overs means 312 needed from 46.2 overs — 6.73 per over, with the anchor gone. That is the arithmetic that sets the temperature of a final, and the report never writes it.

On top of that sits a detail that speaks to the report's assembly. One line says Pakistan was 'pursuing 326'; another says Sri Lanka was 'defending a total of 326'. If the score is 326, the target is 327 — a one-run discrepancy that indicates the piece was assembled without statistical sub-editing. It does not prove the figures wrong; it means the rest deserve the same scrutiny.

Core: One trap, three juggles, and a 326 built by two men

1. The field arrived before the ball

The report says Madushanka floated a delivery to lure Babar into a cover drive; Babar tried to get to the line, edged it, and the fourth slip was already there.

That is not a description of accident. That is a description of design. The recipe for a sucker ball in pace bowling is always the same — full length, outside off, a hint of away movement, so the batter's body is drawn to the line and the hands push ahead of it. The instant a batter reaches for the line, half his control is gone.

The ball alone is never enough. Whether the edge carries is decided by the presence of a fourth slip, because a field setting is the permission to attack; the delivery is the execution of that permission. With a catcher there, the bowler can take a risk he otherwise could not.

Only two fielders are allowed outside the circle in the first ten overs — which is precisely why a fourth slip is available. The law itself permits the trap. The captain's real examination, then: defending 326, in the first powerplay, with boundaries leaking, does he keep a fourth catcher? Sri Lanka did. That single decision reads out the captaincy's whole temperament — this was not containment cricket, it was wicket-taking cricket.

I think of Trent Bridge in 2026, sitting close enough to the sightscreen to track Kuldeep Yadav's wrist position through a 6/25 spell. A wrist can turn a match before the scoreboard admits it. Same here: fielding positions announce the captain's game before the scoreboard does.

2. The technical truth of the catch: a ball that needed three juggles

Three words in the report carry the most weight — the ball 'got big' on him. Shoulder height at fourth slip, the outermost edge of the cordon, where the ball climbs fastest and the hands arrive latest.

Then three juggles. Then completion on the fourth attempt.

That is a description of a brilliant catch and, simultaneously, of a technical flaw. The standard high-catch technique is hands up, fingers splayed upward, absorbing the ball with soft hands. When a catch spills three times, the usual cause is one of two things: the hands went up late, or the weight sat on the fingers instead of the palm. It is the error that humiliates you on the field and disappears in practice.

The tape does not lie; it just waits to be asked. The tape will say the catch was completed — and it will also say it was not completed first time. In fielding analysis that gap matters, because a final-winning catch and a coachable technique are two different objects.

I remember 2026, when the freelance floor vanished — nine commentary shifts cancelled between March and June — and I did what I always do with fear: I went to the tape. In a Mylapore flat I logged 1,400 balls of India's 36 all out in Adelaide, coding every dismissal by seam position and trigger movement. The 9,000-word autopsy ran in January. The lesson was consistent: the moment that looks spectacular on camera usually turns out, at quarter speed, to be a technical deviation. Rathnayake's three-juggle catch belongs in that category.

3. 208 out of 326: a two-man total

Look at the innings' architecture. Kamindu Mendis 131 off 128; Rathnayake 77 off 65. Together 208 runs — roughly 64 per cent of the total, of which 146 came in a single stand.

That concentration was the day's strength and the structure's warning. If two batters are producing two-thirds of a team's runs in a tri-series final, the direct implication is that the other six made one-third between them — which is a red flag for the day one of the two falls early.

Look at the depth of the innings. Rathnayake's strike rate was 118.5 against a team rate of about 6.5 an over. He out-paced his own innings by roughly 1.8 times. This is a tempo-setting innings, not merely an accumulating one. Modern ODI top-order benchmark sits at 90–100; 118.5 is clearly above it.

There is a fine print too. Eight fours, 32 runs, 41.6 per cent of his output. No sixes reported. The rest: 45 runs off 57 balls, a strike rate of 78.9. That profile says his scoring leans on placement and gaps rather than power — a profile that travels better in 50-over cricket than in T20 death roles.

4. The skill that never appears on the auction sheet

Rathnayake proved two different kinds of asset in this final: the series' leading run-scorer, and a specialist fourth-slip catcher in a final.

In February 2026 I sat in a Bengaluru auction room with a 40-page dossier on 217 players. The room used three pages. Chennai finished ninth, four wins in fourteen. The lesson from that room: the auction sheet buys runs and strike rates; it does not price the ball held at slip. Slip catching is a discrete, coachable, thinly-supplied skill — and teams never pay for it separately.

That is where Rathnayake's selection value rises. Compared with a pure batter of equal output, a player carrying specialist slip fielding has a more durable place in the side. This is direct cricket-economics: the price of a scarce skill is set not by its visibility but by its scarcity.

The age curve supports it. At 24 he is pre-peak — batters conventionally peak between 27 and 33 — so a rising output curve is structurally plausible rather than a late-career spike. Then the brake: his career average and strike rate are absent from the report, which means the 77 off 65 cannot be benchmarked against his own baseline. Without that number, this is a good innings, not evidence of a step change.

5. Babar: the number nobody wrote

Babar fell to the fourth ball of the fourth over with the side at 14/2, which means his score was in single figures — nought, or somewhere between one and six. The report withholds the actual figure. In a 'superstar dismissed' narrative that omission is convenient, because the 14/2 tableau is dramatic enough on its own.

I will not do the temperament line here. My first question is always what the system was doing before the ball was bowled, and the answer is that the system was luring him. A required rate of 6.52, an early overs context, a ball leaving him, and a catcher at fourth slip. In that setting, leaving the ball is the hardest act available, because leaving does not move the score and the chase grows heavier. He played the shot that the field setting made cheapest.

Contrarian: the catch did not win the final — and we have no way of knowing

Now the part that belongs to the file rather than the field. The report calls the catch 'sensational', and the language quietly assumes it turned the match. There is no verified basis for that claim, because the result of the final is not recorded at all. What we know is a state, not an outcome: 312 needed off 278 balls with the anchor gone — 6.73 an over.

That is heavy pressure. It is not a win. And the gap between those two is where most cricket writing contaminates itself. If the remaining batters completed that 6.73, the catch becomes a fine image from a fine game rather than the decisive moment. If they did not, the credit for the delivery and the credit for the catch still belong to two separate men.

And here is the real blind spot: we joined the result to the consequence while holding no information about the result. The error is common because the catch is visible and the field setting is not. A catch is a camera subject; a trap is a coach's subject.

Second, a point the commentary box never reaches. The delivery had two failure points, and Sri Lanka cleared both. First, the bowler had to hit the line — outside off, full, a hint of deviation. A ball angled in and the fourth slip is decoration. Second, the catch had to be completed — and it slipped three times. One floated ball, one edge, one juggled catch. Had any of the three failed, this article would not exist. When a cricket story rests on a single point of execution, calling it a structural victory deserves a second thought.

Third, the most uncomfortable observation here. Sixty-four per cent of Sri Lanka's innings came from two batters. In a final that can win you a trophy. Across a tri-series it is a structural warning, because it means the total hangs on two men's form rather than on a system. The day Kamindu or Rathnayake falls in the second over, the side will be under 200 — and there will be no total to defend with catches.

An access note belongs here, since I work with both boards and franchises: the rule I have used in this piece — that a fourth slip is permitted inside the powerplay — is the code's, not an advisor's, and I checked it against the playing conditions rather than against a source's mood. Where the report is silent, I have written 'insufficient information' rather than inferred.

Takeaway: what to watch next

Next match, when Pakistan bat in the powerplay, do not watch the score — watch the cordon. If Sri Lanka keeps a fourth catcher, the thinking is structural. If they drop back to three, the fourth slip in Lahore was an occasion decision, not a policy.

Two things to track on Rathnayake: first, the six count, because a profile of eight fours and no sixes will need more balls to reach a big score; second, his career strike rate, to establish whether 118.5 is a new level or a good day.

And the largest question Lahore leaves open: will a final win built on two batters and one catch be read as a step forward — or will that 64 per cent be read as the most important number of the tournament? The structure's answer arrives in the next series, when the cameras are on Sri Lanka's middle order and the fourth slip is empty.