Dejected Babar Azam kneels beside his bat as Pakistan’s players walk away and West Indies celebrate their first Test victory with jubilant home fans.

Babar Azam Left Stranded as West Indies Pacers Script Big Win in 1st Test Against Pakistan

Babar Azam carried his bat for an unbeaten 58, but Pakistan’s batting collapsed around him as Jayden Seales powered West Indies to a 90-run victory in the first Test at Tarouba.

Published

1 day ago

July 28, 2026

Jeremy Montes

West Indies defeated Pakistan by 90 runs at the Brian Lara Cricket Academy after Jayden Seales claimed five wickets and Babar Azam carried his bat for an unbeaten 58 in a failed chase of 211.

Babar Azam stood at one end for nearly three and a half hours, watching Pakistan’s pursuit of 211 disintegrate around him.

He survived the new ball, reached his half-century, fought through the pressure created by a rapidly shrinking batting order, and even found unlikely support from Mohammad Abbas. None of it was enough.

West Indies dismissed Pakistan for 120 in 40.2 overs to win the first Test by 90 runs at Tarouba and take an unassailable 1-0 lead in the two-match series. The result also handed the hosts 12 ICC World Test Championship points while Pakistan left the inaugural Test at the Brian Lara Cricket Academy with nothing.

Jayden Seales finished with 5-20 from 14.2 overs, including six maidens, while Justin Greaves followed his first-innings five-wicket haul with another two crucial wickets. Kemar Roach removed two batters, and Shamar Joseph accounted for one as the West Indies pace attack shared all 10 wickets.

The scorecard will show another Pakistan batting collapse. The deeper story concerns the isolation of Babar, the physical limitations affecting first-innings centurion Shan Masood, and a batting lineup that failed to match the discipline shown by its own bowlers.

West Indies vs Pakistan 1st Test scorecard

Team	First innings	Second innings	Result
West Indies	311	181	Won by 90 runs
Pakistan	282	120	Target: 211

Player of the Match: Justin Greaves, 5-27, 20 and 2-12
West Indies’ leading batter: Shai Hope, 92
Pakistan’s leading batter: Shan Masood, 109
Best bowling figures: Mohammad Abbas, 5-22
Series position: West Indies lead 1-0 with one Test remaining
WTC points: West Indies 12, Pakistan 0

Babar Azam fights alone as Pakistan collapse

Pakistan began the final innings requiring 211, a challenging target on a surface that continued to reward accurate fast bowling but one that still appeared reachable if the top order could absorb the opening spells.

That hope lasted only a few overs.

Imam-ul-Haq edged Roach behind for three at 5-1. Test debutant Azan Awais followed for the same score after Seales found his outside edge. Salman Agha was trapped lbw for a six-ball duck, leaving Pakistan 25-3 inside eight overs.

By lunch, they were 28-3. Babar had already become the central figure in the chase, not because Pakistan had constructed a platform for him, but because nearly every other specialist batter had failed to stay with him.

Mohammad Rizwan offered brief resistance before Greaves bowled him for 11. Aamer Jamal was trapped lbw for a 12-ball duck by the same bowler. Roach then removed Ali Usman for two, reducing Pakistan to 53-6.

Six wickets had fallen before the team reached one-quarter of its target.

Babar continued to leave carefully outside off stump and punished the occasional loose delivery. His nine boundaries came without reckless expansion or desperate slogging. He reached 50 from 81 balls, but the milestone carried little celebration because Pakistan were already nine wickets down.

The series had begun as a red-ball reset under Babar’s restored captaincy. His unbeaten 58 showed the technical control and personal responsibility Pakistan needed from him. The innings also revealed how little support existed around the captain when the match reached its most demanding phase.

Shan Masood’s injury changed Pakistan’s chase

The most damaging absence was not recorded as a missing name on the scorecard.

Shan Masood had scored a gritty 109 in Pakistan’s first innings, becoming the first Test centurion at the Brian Lara Cricket Academy. His 155-run partnership with Imam brought Pakistan back from 1-1 and created an opportunity to move beyond West Indies’ 311.

An injury, however, prevented Masood from occupying his usual position at the top of the order in the chase. By the time he entered at No. 8, Pakistan were already 53-6 and the original structure of the innings had disappeared.

Masood attempted to survive rather than dominate. He made three from 15 balls before Seales removed him, with Shamar Joseph taking the catch.

It would be unfair to claim Masood alone would have carried Pakistan to 211. The West Indies quicks were too accurate, and the rest of Pakistan’s batting was too fragile for one hypothetical partnership to erase every problem.

Still, his injury had a major tactical cost. Pakistan lost the opener who had spent 184 balls understanding the pitch in the first innings. Babar was denied the teammate best equipped to share the new-ball burden, manage the chase and build a serious partnership.

The contrast was painful. Masood had provided Pakistan’s longest and most important innings of the match. When the same team needed him again, he could only appear after six wickets had fallen.

Mohammad Abbas exposes the scale of Pakistan’s batting failure

The most revealing Pakistan statistic did not belong to Babar or Masood.

Mohammad Abbas scored 23 from 33 balls and became the team’s second-highest scorer in the fourth innings. His contribution was also the joint fourth-highest individual score by a Pakistani across the entire Test.

That figure explains the defeat more clearly than any tactical theory.

Only Babar, Abbas and Rizwan reached double figures during the chase. Five players were dismissed for two runs or fewer, including three ducks. Pakistan’s nine dismissed batters contributed just 49 runs between them.

Abbas joined Babar at 71-9 and helped add 49 for the final wicket, the largest partnership of the innings. The stand delayed West Indies and took Pakistan from complete humiliation to a slightly more respectable total, but it never placed the outcome in genuine doubt.

The end came when Seales brought one back into Abbas and struck his front pad. The batter reviewed the decision, but ball tracking showed the delivery brushing the outside of leg stump. The umpire’s call stood, giving Seales his fourth Test five-wicket haul and confirming West Indies’ 90-run victory.

Justin Greaves broke Pakistan twice

Seales delivered the decisive spell on the final day, but Justin Greaves had already altered the direction of the Test.

Pakistan appeared well placed at 244-4 in their first innings, with Masood completing his seventh Test century. A substantial lead remained possible. Greaves then dismantled the lower order with a remarkable sequence of five consecutive wicket-maiden overs.

Masood, Jamal, Ali Usman, Rizwan and Abbas all fell to Greaves as Pakistan lost five wickets for 23 runs. More specifically, five wickets disappeared for 15 runs between 244-4 and 259-8.

Pakistan eventually reached 282, conceding a 29-run first-innings lead when they had briefly looked capable of controlling the match. Greaves finished with 5-27 from 11 overs, including six maidens.

He returned in the second innings to dismiss Rizwan and Jamal, ending the match with seven wickets and 20 useful runs.

“This performance is right up there,” Greaves said after receiving the Player of the Match award. “I put my best foot forward whenever it is about to get the team over the line.”

His performance supported the advantage he created with his first-innings five-for. West Indies did not simply wait for Pakistan to collapse. Greaves manufactured the opening and Seales finished the job.

Pakistan’s fast bowlers deserved a better result

Pakistan’s decision to reshape the bowling attack largely worked.

Mohammad Abbas, Khurram Shahzad, Mohammad Ali and Aamer Jamal took all 20 West Indies wickets. None relied on extreme speed. They succeeded through seam movement, control and sustained pressure.

Mohammad Ali collected 4-50 in the first innings, while Abbas produced 5-22 from 15.5 overs in the second. West Indies slipped to 93-7 before Shamar Joseph changed the complexion of the match with 38 from 27 balls.

Joseph struck four sixes and added 61 with Roach for the eighth wicket. Those lower-order runs lifted West Indies to 181 and pushed the target to 211. On a better batting surface, that partnership might have been treated as a useful bonus. At Tarouba, it proved decisive.

Abbas deserved more than defeat after taking eight wickets in the match and contributing the second-highest score in Pakistan’s chase. His 5-22 also placed him on the venue’s first Test honours board alongside Masood, Greaves and Seales.

Pakistan’s bowlers completed their primary assignment by taking 20 wickets. The batting unit failed to convert that work into a competitive result.

All 40 wickets fall to fast bowling at Tarouba

The inaugural Test at the Brian Lara Cricket Academy produced a remarkable piece of Caribbean history.

According to former West Indies leg-spinner Samuel Badree, this was the first Test in the Caribbean in which fast bowlers claimed all 40 wickets.

West Indies selected Jomel Warrican, but the left-arm spinner bowled 18 overs across the match without taking a wicket. Pakistan’s specialist slow bowler, debutant Ali Usman, was also wicketless.

The match belonged to seam movement, disciplined lengths and batters’ ability to survive repeated examination around off stump. Greaves and Seales earned five-wicket hauls for West Indies, while Abbas registered Pakistan’s only five-for.

The milestone added further significance to the first Test staged at a venue more familiar with white-ball cricket. Tarouba’s opening red-ball contest immediately produced its own identity.

Pakistan’s away Test crisis gets worse

The defeat extended Pakistan’s run to eight consecutive Test losses away from home. They have now gone three years without an overseas Test victory.

That record cannot be blamed on one difficult pitch, one injury or one destructive spell.

Pakistan entered the series after returning the Test captaincy to Babar Azam. Leadership changed, the pace attack changed, and younger players were given opportunities. The same batting weaknesses remained visible when the ball moved and the match demanded patience.

The visitors lost six wickets for 38 runs after reaching 244-4 in the first innings. They then collapsed to 71-9 in the second. Those were separate innings, but the underlying issue was identical: once a set batter or established partnership disappeared, Pakistan had no mechanism for slowing the collapse.

The second Test offers a chance to draw the series, but Pakistan cannot win it. West Indies have already secured at least a share of the contest and will enter the final match with greater confidence in both their pace attack and lower-order resilience.

Final verdict: Babar stayed, but Pakistan never built around him

Babar’s unbeaten 58 will be remembered as a captain’s resistance, although it could not become a match-winning innings because Pakistan never gave it the necessary support.

Masood’s injury removed the batter best prepared to stand beside him. Rizwan was the only specialist teammate to reach double figures, and Abbas had to perform a role that should never have fallen to the No. 11.

West Indies were sharper in the passages that defined the match. Hope and Hodge built the first-innings total, Joseph and Roach stretched the lead when Pakistan threatened to regain control, Greaves destroyed the first innings, and Seales settled the second.

Pakistan also produced four worthy individual performances through Masood, Babar, Abbas and Mohammad Ali. The difference was that West Indies connected their contributions. Pakistan’s best efforts remained isolated.

Babar was the last specialist batter standing. By the time Abbas was struck on the pad at 120, he was also the only Pakistani left with whom the captain could have continued the fight.

That final image captured Pakistan’s Test more accurately than the 90-run margin: Babar unbeaten at one end, his teammates gone, and another away match slipping into a familiar pattern.

Explore more cricket news and analysis from The Sports Encounter, including our examination of what history suggested about Pakistan’s fourth-innings chase and the wider legacy of Pakistan’s greatest Test-era performances against West Indies. Full match figures can be reviewed through the official first Test scorecard.

Up Next

Myanmar Punish Philippines 4-1 as Group B Race Finds Its First Real Twist

Don't Miss

Ibrahim Zadran Finds His Rhythm as Jaffna Kings Punish Colombo’s Costly Mistakes

Jeremy Montes

Jeremy Montes is a Chile-based sports writer covering soccer, the Olympic Games, and regional sports across South America. His work explores major tournaments, athlete performances, emerging talent, and the powerful relationship between sport, national identity, and supporters throughout the continent.

Breaking News

Duckett Returns to Cardiff and Leaves Welsh Fire Counting the Cost

Ben Duckett’s unbeaten 52 helped Trent Rockets chase 123 in only 72 balls after Mitchell Santner and Matt Henry dismantled Welsh Fire in Cardiff.

Published

5 hours ago

July 29, 2026

Elma Victors

Duckett Returns to Cardiff and Leaves Welsh Fire Counting the Cost

Welsh Fire had started The Hundred with two straight wins and the kind of confidence that made Cardiff feel like a difficult place for visiting teams. By the end of Wednesday afternoon, the home crowd had watched that early momentum disappear in only 72 balls.

Ben Duckett, once a Welsh Fire batter himself, returned to Sophia Gardens and guided Trent Rockets to a commanding nine-wicket victory on July 29. His unbeaten 52 provided the control, Finn Allen supplied the early force, and Tom Banton completed a chase that never developed into a contest.

Trent Rockets reached 126 for one with 28 balls remaining after restricting Fire to 122 for seven. The margin lifted the Rockets into second place in the early standings and pushed Welsh Fire down to fifth on net run rate, despite both teams holding eight points.

TL;DR

Trent Rockets defeated Welsh Fire by nine wickets with 28 balls remaining.
Welsh Fire scored 122 for seven from their 100 balls.
Ben Duckett won Player of the Match after making an unbeaten 52.
Finn Allen struck 33 from 19 balls and attacked during the decisive opening partnership.
Mitchell Santner took three wickets, while Matt Henry claimed two for 16.
Matthew Short top-scored for Welsh Fire with 36 from 26 balls.
Seven no-balls damaged Fire’s attempt to defend an already modest total.
Trent Rockets moved to second place, while Welsh Fire dropped to fifth on net run rate.

Welsh Fire vs Trent Rockets Match Scorecard

Detail	Information
Competition	The Hundred Men’s Competition 2026
Match	Welsh Fire vs Trent Rockets, Match 11
Date	July 29, 2026
Venue	Sophia Gardens, Cardiff
Toss	Trent Rockets elected to bowl
Welsh Fire	122/7 from 100 balls
Trent Rockets	126/1 from 72 balls
Result	Trent Rockets won by nine wickets
Balls Remaining	28
Player of the Match	Ben Duckett, 52 not out
Welsh Fire Top Scorer	Matthew Short, 36 from 26 balls
Trent Rockets Top Bowler	Mitchell Santner, 3/35
Turning Point	Welsh Fire slipped from 62/2 to 72/5
Table Impact	Rockets rose to second; Fire dropped to fifth

Matt Henry Breaks Welsh Fire’s Early Rhythm

Phil Salt had already shown his ability to manage difficult situations during Welsh Fire’s opening win over Southern Brave, when his unbeaten 47 completed a measured chase. That control never emerged against Trent Rockets.

Matt Henry removed Salt for five and then bowled Joe Root for the same score, leaving Fire at 26 for two after 24 balls.

The early wickets prevented Welsh Fire from using their powerful middle order on their own terms. Matthew Short responded with 36 from 26 deliveries, including one four and two sixes, but he spent much of his innings repairing damage rather than building toward a large total.

His 36 became the highest score of the innings. Once Lewis Gregory removed him with the score at 62, Welsh Fire lost the batter who had provided their clearest route toward 150.

The home side’s earlier victories had been built around stronger partnerships. Phil Salt had anchored the win over Southern Brave, while Rachin Ravindra’s 98 powered Fire past MI London. Trent Rockets denied them both elements by taking regular wickets and controlling the center of the innings.

Fans can revisit Salt’s disciplined opening performance in The Sports Encounter’s report on Welsh Fire’s win over Southern Brave.

Santner Turns Pressure Into a Collapse

The match shifted decisively after Short’s dismissal.

Mitchell Santner removed Rachin Ravindra for 16 and then struck again three balls later when Marco Jansen departed. Welsh Fire fell from 62 for two to 72 for five, losing three wickets for 10 runs during the most damaging phase of their innings.

Santner’s value came from his control as much as his wickets. He varied his pace, kept the ball away from the strongest hitting zones, and forced Welsh Fire’s batters to manufacture power.

Jordan Cox offered the only serious late response. He struck four sixes in a rapid 33 from 16 balls and briefly threatened to pull the total toward something defendable.

Santner ended that resistance as well. Cox drove another attacking shot toward deep extra cover, where Finn Allen completed the catch. The dismissal left Fire at 110 for six and removed their final realistic chance of producing a strong finish.

Santner completed his spell with three for 35. Henry’s two for 16 had created the early damage, while Santner controlled the phase where Fire needed to recover.

Welsh Fire eventually reached 122 for seven, a total that looked light even before Trent Rockets began their chase.

Finn Allen Removes the Pressure Immediately

Trent Rockets approached 123 as a target to attack rather than manage.

Duckett found an early boundary, but Allen supplied the acceleration. The New Zealand opener attacked Sam Cook for 17 runs during one five-ball set, hitting two sixes and a four.

That sequence carried Trent Rockets to 59 without loss after 30 balls and effectively removed the required rate from the match.

Allen scored 33 from 19 deliveries before Ravindra trapped him leg before. By then, the opening pair had added 75 runs and reduced the target to 48 from 75 balls.

The wicket offered Welsh Fire little encouragement. Tom Banton entered with complete freedom and struck an unbeaten 31 from only 15 deliveries.

Trent Rockets’ top order had already shown its scoring depth in a 418-run contest against Birmingham Phoenix, although Joe Clarke and Will Smeed’s efforts could not prevent a 10-run defeat. The Sports Encounter covered that remarkable match in its report on Birmingham Phoenix’s win over Trent Rockets.

This time, the Rockets’ batters had far less work to do.

Duckett Controls the Chase Against His Former Team

Duckett’s innings lacked the urgency of Allen’s opening assault, but it gave the chase structure.

The left-hander finished unbeaten on 52 from 45 balls, ensuring that Welsh Fire never found a second opening. He rotated the strike, punished width, and allowed Allen and Banton to attack around him.

His fifty carried added interest because Duckett previously represented Welsh Fire before joining Trent Rockets for the 2026 competition. Cardiff knew his range of scoring options. Welsh Fire’s bowlers still could not prevent him from controlling the chase.

Banton sealed the result with a boundary through long-off on ball 72.

The winning partnership reached 51 from 30 balls. Trent Rockets finished on 126 for one, with Duckett unbeaten and Banton scoring at more than two runs per delivery.

Welsh Fire’s Seven No-Balls Remove Any Hope of a Comeback

Defending 122 required accuracy, early wickets, and sustained scoreboard pressure.

Welsh Fire delivered none of the three consistently enough.

Their attack bowled seven no-balls during the innings, gifting Trent Rockets extra runs and extra deliveries. Lockie Ferguson overstepped twice during a costly set, while other bowlers also struggled with their front-foot discipline.

The errors mattered because they prevented Fire from building sequences of dot balls. Even when the bowlers found a good length, the additional deliveries allowed Allen and Duckett to reset the pressure.

The seven no-balls did not single-handedly decide the match. Welsh Fire had already posted too few runs. However, they removed whatever slim chance remained of forcing the Rockets into an uncomfortable chase.

Updated Men’s Hundred 2026 Points Table

Position	Team	Played	Won	Lost	Points	Net Run Rate
1	Manchester Super Giants	3	2	1	8	+1.194
2	Trent Rockets	3	2	1	8	+0.824
3	MI London	3	2	1	8	+0.183
4	Sunrisers Leeds	3	2	1	8	+0.032
5	Welsh Fire	3	2	1	8	-0.427
6	Birmingham Phoenix	2	1	1	4	-1.925
7	Southern Brave	3	0	3	0	-0.201
8	London Spirit	2	0	2	0	-0.275

The table shows how heavily the nine-wicket margin affected both teams.

Trent Rockets climbed to second because completing the chase in 72 balls significantly improved their net run rate. Welsh Fire remained level with four teams on eight points but fell to fifth after their NRR dropped below zero.

The early standings remain crowded. The format rewards only the top three teams, with the league leader moving directly into the final and the next two contesting the eliminator. Every major defeat can therefore carry consequences beyond the immediate loss.

Readers can track the wider competition through The Sports Encounter’s Cricket Hub and its report on Marsh and Brook’s record chase for Sunrisers Leeds.

What Comes Next for Welsh Fire and Trent Rockets?

Trent Rockets leave Cardiff with two consecutive victories after recovering from their opening loss against Birmingham Phoenix. Their bowling looks balanced, Duckett has found form, and Allen gives the top order immediate attacking power.

They next face Manchester Super Giants at Old Trafford on July 31, a match that could determine who controls the top of the table.

Welsh Fire travel to Edgbaston to face Birmingham Phoenix on August 1. Their first defeat does not undo an encouraging start, but the manner of it requires attention.

The batting unit lost too many wickets through the middle. The bowlers then compounded the problem with repeated no-balls.

Welsh Fire had looked like one of the competition’s most settled teams during victories over Southern Brave and MI London. Trent Rockets exposed how quickly that authority can disappear when early wickets, middle-order pressure, and poor discipline arrive together.

For more franchise-cricket reporting, readers can also explore The Sports Encounter’s coverage of Nicholas Pooran’s explosive Hundred opener and Will Jacks’ last-ball win over Southern Brave. Official fixtures and competition updates are available through The Hundred.

Final Takeaway

Trent Rockets won this match during two decisive periods.

Henry and Santner turned Welsh Fire’s innings into a struggle, reducing a promising 62 for two into 72 for five. Allen then attacked hard enough during the chase to ensure Duckett could manage the rest without risk.

Duckett earned the Player of the Match award and owned the finish. The deeper story belonged to the difference in discipline.

Trent Rockets bowled to a plan and chased with clarity. Welsh Fire lost wickets in clusters, posted 122, and then offered seven extra deliveries while trying to defend it.

In a league where five teams finished the day level on eight points, that combination carried a heavy price.

Breaking News

Akeal Hosein Nearly Steals It, but Desert Vipers Escape in Final Over

Rilee Rossouw mastered a difficult Providence pitch before Desert Vipers survived Akeal Hosein’s four-wicket fightback to beat Perth Scorchers XI by one wicket.

Published

15 hours ago

July 29, 2026

Marcos Wetherfield

Akeal Hosein Nearly Steals It, but Desert Vipers Escape in Final Over

Nine runs from nine balls should have felt manageable. With only one wicket remaining and Akeal Hosein turning every delivery into a threat, Desert Vipers could feel the match closing around them.

Nathan Smith finally broke the tension with a boundary from the penultimate ball, carrying the Vipers to a one-wicket victory over Perth Scorchers XI at Providence Stadium on July 28.

Rilee Rossouw had made the chase possible with a controlled 50 from 31 balls on a surface where timing rarely came easily. Yet the match’s most complete performance belonged to Hosein, who scored an unbeaten 32 before taking 4 for 15 and dragging Perth to the edge of an improbable defense.

The Vipers reached 113 for 9 after Perth had posted 112 for 6, ending one of the closest matches of the Global Super League 2026 campaign with one delivery unused.

TL;DR

Desert Vipers defeated Perth Scorchers XI by one wicket.
Perth scored 112 for 6, with Andre Fletcher making 40 and Akeal Hosein finishing unbeaten on 32.
Rilee Rossouw anchored the chase with 50 from 31 balls.
Hosein took 4 for 15 and triggered a dramatic Vipers collapse.
Perth claimed three wickets for one run in seven balls late in the chase.
Nathan Smith hit the winning boundary with one ball remaining.
The defeat ended Perth’s hopes of reaching the GSL finals.

Desert Vipers vs Perth Scorchers XI Scorecard

Detail	Information
Competition	Global Super League 2026, Match 8
Match	Desert Vipers vs Perth Scorchers XI
Venue	Providence Stadium, Guyana
Date	July 28, 2026
Perth Scorchers XI	112/6 in 20 overs
Desert Vipers	113/9 in 19.5 overs
Result	Desert Vipers won by one wicket
Top Batter	Rilee Rossouw, 50 off 31 balls
Best Bowler	Akeal Hosein, 4/15 in four overs
Perth Standouts	Andre Fletcher 40, Akeal Hosein 32, Ashton Agar 17
Turning Point	Perth took three wickets for one run in seven balls
Winning Moment	Nathan Smith’s boundary from the penultimate ball
Tournament Impact	Perth eliminated; Vipers remain in the finals race

Perth’s Top Order Struggles Against Spin

Perth’s problems began before the innings had developed any rhythm.

D’Arcy Short made five and Joel Curtis scored one as the Scorchers slipped to 14 for 2 inside four overs. Usman Khan followed for a low score in the seventh, leaving Perth at 32 for 3 on a pitch that rewarded slower bowling, accurate lengths, and patience.

Khary Pierre caused the early damage with his left-arm spin. Vitel Lawes also found enough grip to prevent Perth from attacking freely through the middle overs.

Andre Fletcher responded with the innings’ first meaningful counterattack. His 40 gave Perth a batter willing to use his feet, challenge the boundary, and prevent the Vipers from squeezing the innings completely.

Fletcher shared a 36-run fourth-wicket stand with Hosein, but his dismissal immediately after hitting the innings’ first six prevented Perth from building a larger surge. Lawes removed him at deep midwicket and restored the Vipers’ control.

The Scorchers had faced similar batting pressure earlier in the competition. Their tournament began with a 16-run defeat covered in The Sports Encounter’s report on Farhan Yousaf’s match-winning GSL debut.

Akeal Hosein Gives Perth a Fighting Total

Hosein understood the pitch better than most batters.

Rather than forcing risky strokes against the turn, he waited for deliveries he could place into gaps and kept the innings moving. His unbeaten 32 gave Perth enough stability to survive the middle overs and reach a defendable total.

Ashton Agar provided useful support with 17 not out from 11 balls. Their late contributions pushed Perth to 112 for 6, a modest score in ordinary T20 conditions but a competitive one at Providence.

Lawes finished with 2 for 18, while Pierre took 2 for 14. Shadab Khan added 1 for 16 as the Vipers’ spinners controlled the scoring rate and denied Perth a conventional death-overs acceleration.

The low total reflected the wider demands of franchise cricket on difficult surfaces. Readers can follow more tactical T20 analysis through The Sports Encounter’s Cricket Hub and its coverage of Lahore Qalandars’ win over Desert Vipers.

Rossouw Solves the Pitch Before Perth Fight Back

The Vipers’ chase began almost as badly as Perth’s innings.

Saiteja Mukkamalla fell in the third over, and Desert Vipers slipped to 31 for 3 during the powerplay. Perth’s bowlers attacked the stumps, varied their pace, and forced the chasing side to create its own scoring opportunities.

Rossouw changed the tempo without losing control.

The experienced left-hander struck four fours and three sixes in his 50 from 31 balls. His innings mattered because he identified which deliveries could be attacked and refused to let the required rate become another source of pressure.

Rossouw’s fifty moved the Vipers toward 85 for 5 in the 14th over. At that stage, the chase appeared uncomfortable but stable.

His approach offered a contrast to Perth’s top order. Rossouw did not wait for the pitch to become easier. He adjusted his scoring areas, targeted favorable matchups, and accepted that several overs would produce singles rather than boundaries.

Hosein’s Four-Wicket Spell Changes the Match

Hosein then took control with the ball.

His accuracy became even more dangerous as the Vipers tried to close the chase. He finished with 4 for 15 from four overs, repeatedly forcing batters to play across deliveries that gripped or held their line.

Sufyan Moqim supported him with 1 for 17, while Brody Couch produced an important direct-hit run-out to dismiss Vriitya Aravind.

Perth’s pressure reached its peak when it claimed three wickets for one run in seven deliveries. The Vipers went from approaching a controlled finish to needing nine runs from nine balls with only their final pair remaining.

That sequence became the match’s true turning point. Rossouw had built the platform, but Hosein made the result uncertain again.

The Scorchers had already shown their ability to remain competitive after difficult starts, including their fight against Lahore. The larger problem throughout the tournament was completing those recoveries.

Nathan Smith Finds the Final Boundary

Perth continued attacking the stumps and protecting the boundary as the final over began.

The Vipers could not afford another mistake. Their last pair needed to balance survival with enough intent to prevent the equation from reaching the final delivery.

Smith eventually found the release.

His boundary from the fifth ball of the final over carried Desert Vipers past 112 and ended Perth’s resistance. The winning shot produced relief rather than celebration at first, reflecting how close the Vipers had come to losing a chase Rossouw had placed under control.

What the Result Means for Both Teams

The defeat officially ended Perth Scorchers XI’s chances of reaching the GSL finals. They still had one league match remaining against Guyana Amazon Warriors, but their qualification route had disappeared.

For the Vipers, the victory kept their tournament alive after an uneven campaign. They had previously lost to Lahore Qalandars but recovered with important wins as the league stage tightened.

Their ability to handle pressure remains a concern. A chase of 113 should not usually require the final wicket and the penultimate ball, even on a difficult pitch.

Still, tournament cricket rewards completed victories more than comfortable explanations.

The Sports Encounter has tracked the competition from its opening round, including Rovman Powell’s tense chase for Guyana and Lahore’s second victory behind Michael Bracewell and Usama Mir. Broader franchise and international coverage is available through our latest sports analysis.

Final Takeaway

Rossouw played the innings that won the match, but Hosein produced the performance that defined it.

His unbeaten 32 gave Perth something to defend. His four wickets then converted a modest total into a genuine threat.

Desert Vipers survived because Rossouw solved the pitch early enough and Smith found the boundary when no room remained for another error.

Perth leave with another defeat, yet their late fight showed how close discipline and belief can bring a team to defending 112. The Vipers leave with the points, the relief, and a reminder that their next high-pressure chase may demand a cleaner finish.

Breaking News

‘Clicky Ponting’ Cricket Scandal Explained: How a Finger Click Allegedly Created a Fake Wicket

An English amateur cricketer is accused of clicking his fingers to imitate an edge and deceive an umpire. We explain the incident, MCC Law 41 and the sanctions that may follow.

Published

1 day ago

July 28, 2026

Jawad Hussain

A viral club cricket video appears to show a close-in fielder clicking his fingers as the ball passes the bat, allegedly creating a false edge sound that helped convince the umpire to give the batter out. The incident is now under formal investigation.

A strange dismissal in English amateur cricket has raised serious questions about deception, umpiring and the Spirit of Cricket.

The North Yorkshire and South Durham Cricket League has opened an investigation following a formal complaint about alleged incidents during a Division Two match between Saltburn Cricket Club’s second XI and Norton Cricket Club’s second XI on Saturday, July 25, 2026.

Video footage circulating online appears to show a Saltburn close-in fielder clicking his fingers at almost the exact moment the ball passes the batter’s outside edge. The wicketkeeper catches the delivery, the fielding side appeals and the umpire raises his finger.

The batter, reportedly Noman Shabir, immediately appears confused by the decision and gestures toward the nearby fielder. His reaction suggests he believed the sound heard by the umpire came from the finger click rather than contact between bat and ball.

Saltburn won the match by 159 runs. However, the result has been overshadowed by an allegation that goes far beyond an umpire making an ordinary mistake.

If the finger click was deliberate and intended to imitate the sound of an edge, it would represent an attempt to manufacture evidence for a dismissal.

That is why a brief movement of two fingers has created such a major controversy.

What Happened in the Alleged Finger-Click Incident?

In cricket, a batter can be dismissed caught when the ball touches the bat or a hand holding the bat before being legally caught by a fielder.

During caught-behind appeals, the umpire often relies heavily on sound. A faint edge may produce a small noise that can be difficult to distinguish from the bat hitting the ground, clothing moving or another sound near the wicket.

Professional matches offer technological assistance through tools such as UltraEdge. Most recreational cricket does not have that protection.

The viral video appears to show the following sequence:

The bowler delivers the ball outside the batter’s off stump.
The batter plays at the delivery.
A close-in fielder appears to click his fingers as the ball passes the bat.
The wicketkeeper catches the ball.
Several fielders appeal for a catch.
The umpire gives the batter out.
The batter protests and points toward the fielder.

The allegation is that the finger click simulated the sound of bat hitting ball and influenced the umpire’s decision.

Online users have given the controversy several nicknames, including “Clickgate” and “Clicky Ponting,” a reference to former Australian captain and celebrated slip fielder Ricky Ponting.

The jokes have helped the footage travel around the world, but the underlying accusation is serious. It concerns a possible deliberate attempt to deceive a match official and unfairly remove an opponent from the game.

Readers interested in unusual moments that can influence a dismissal can also examine whether a bee disrupted Joe Root’s concentration immediately before his dismissal.

Finger-Click Controversy at a Glance

Detail	Information
Competition	North Yorkshire and South Durham Cricket League Division Two
Match	Saltburn CC 2nd XI vs Norton CC 2nd XI
Date	July 25, 2026
Allegation	A fielder clicked his fingers to imitate the sound of an edge
Immediate outcome	The batter was given out caught behind
Match result	Saltburn won by 159 runs
League response	Formal investigation opened
Applicable cricket law	MCC Law 41 on unfair play
Possible consequences	Warning, fine, suspension, points deduction or other disciplinary action
Current status	The allegations remain under investigation

Why Would Clicking Fingers Fool an Umpire?

Caught-behind decisions are among the most difficult judgments in cricket, particularly without video or sound technology.

The umpire must watch several things within a fraction of a second:

The bowler’s front foot
The position of the ball
The batter’s movement
Possible contact with the bat
The wicketkeeper’s catch
The fielding side’s appeal

A very thin edge may not visibly change the ball’s direction. Sound can therefore become the strongest clue available to the umpire.

A finger click timed precisely as the ball passes the bat could create a convincing false signal. When that sound is followed by the wicketkeeper catching the ball and several fielders appealing together, the umpire may reasonably connect the noise with an edge.

This is what makes the alleged act especially troubling. It appears designed to exploit the normal limitations of an amateur umpire.

The official has only one chance to make the decision. The fielder, if the allegation is proven, would have deliberately introduced false information into that process.

Cricket regularly produces difficult decisions even when everyone acts honestly. A recent example came when an umpire’s-call decision helped confirm West Indies’ Test victory over Pakistan. That type of judgment is part of the game. Manufacturing an artificial sound would be fundamentally different.

What Does MCC Law 41 Say About Deliberate Deception?

The incident potentially falls under MCC Law 41, which governs unfair play in cricket.

Law 41.4 states that it is unfair for a fielder deliberately to attempt to distract the striker while the batter is preparing to receive or receiving a delivery.

Law 41.5 goes further. It prohibits a fielder from willfully attempting, through words or actions, to distract, deceive or obstruct either batter after the striker has received the ball.

The exact provision applied would depend on when the umpire believed the click occurred. However, deliberate deception is clearly covered by the law.

If an umpire detects such conduct during play, the available response can include:

Calling and signaling a dead ball
Preventing a dismissal from that delivery
Awarding five penalty runs to the batting team
Informing the fielding captain and both batters
Reporting the incident to the relevant cricket authority

Under Law 41.5, the batters may also be credited with any runs completed before the offense and may be allowed to decide which batter faces the next delivery.

The crucial issue is intent. An accidental click, clap or movement would not automatically amount to cheating. The umpire or disciplinary panel would need to determine whether the player acted willfully to create a false impression.

That is precisely what the league’s investigation must establish.

Modern cricket frequently debates whether new playing conditions improve or weaken competitive fairness. The Sports Encounter recently examined that wider issue in its analysis of the IPL Impact Player rule and its effect on genuine all-rounders.

Why Was It Against the Spirit of Cricket?

Cricket’s laws define what players may and may not do. The Spirit of Cricket establishes a wider expectation about how they should behave.

Players can appeal confidently when they genuinely believe a batter is out. They may celebrate, encourage the bowler and apply pressure within the rules.

Creating a false sound to manufacture an edge crosses a different line.

It potentially violates the Spirit of Cricket in several ways.

It Attempts to Deceive the Umpire

The umpire’s decision should be based on what happened during the delivery. Introducing a fake sound deliberately corrupts that decision-making process.

It Denies the Batter a Fair Contest

The batter is entitled to continue batting unless dismissed under the Laws of Cricket. A manufactured edge could end an innings without the ball ever touching the bat.

It Misuses the Appeal System

An appeal asks the umpire to rule on a genuine cricket event. If a player first creates false evidence and then appeals, the appeal becomes part of the deception.

It Exploits the Limitations of Recreational Cricket

Amateur matches rarely have television replays, stump microphones or ball-tracking systems. Fair play therefore depends heavily on honesty among players.

It Damages Trust

Cricket cannot function if every small sound near the bat becomes suspicious. Umpires must be able to trust that fielders are appealing based on what they genuinely saw or heard.

The allegation therefore concerns more than gaining one wicket. It threatens the trust that allows recreational matches to take place.

Cricket has confronted similar questions about legal skill and prohibited manipulation before. The Sports Encounter’s examination of Ian Botham’s career and the historical ball-tampering debate shows how deeply allegations of unfair play can affect reputations long after the match ends.

Readers can follow more controversies, match reports, player comparisons and tactical analysis through The Sports Encounter’s cricket news and analysis hub.

Why the Umpire Should Not Become the Main Target

The footage has led to criticism of the decision, but the umpire should not carry the main blame if deliberate deception is established.

An umpire working without technological assistance must judge a faint edge through sight and sound. A well-timed click could be extremely difficult to identify from the middle.

The official may have heard a noise, seen the ball enter the wicketkeeper’s gloves and observed a confident collective appeal. Those signals normally support a caught-behind decision.

Players also have a responsibility to avoid placing umpires in deliberately manufactured situations.

The investigation should therefore examine the alleged conduct that preceded the decision rather than treating an apparently deceived official as the central offender.

Even at the highest level, officiating controversies can overshadow the actions that produced the decision. The distinction between an official making a reasonable judgment and a participant knowingly creating a false impression must remain clear.

Could the Batter Be Reinstated After the Match?

Usually, an umpire may correct a decision promptly if convinced an error has occurred. Once play has moved on and the match has concluded, reinstating a batter is far more complicated.

The North Yorkshire and South Durham Cricket League is investigating cheating accusations made against an amateur player who is alleged to have clicked his fingers to trick umpires into giving wickets pic.twitter.com/ih8IYeZda0
— Sky News (@SkyNews) July 28, 2026

The dismissal remains part of the official scorecard unless the competition authority uses its regulatory powers to amend the record or match outcome.

A disciplinary panel may punish misconduct without rewriting every event that followed it. Alternatively, league regulations may permit adjustments to points or results if the misconduct materially affected the competition.

No such decision has been announced in this case.

Saltburn’s 159-run victory also means the league would need to consider whether the disputed dismissal had a realistic effect on the final result. The disciplinary issue can remain serious even if officials conclude that Saltburn probably would have won anyway.

Cheating does not become acceptable because the winning margin was large.

What Punishment Could the Player Receive?

The league has not announced a charge, finding or punishment. Any player involved must therefore be treated as innocent unless the allegation is proven through the formal process.

If the investigation concludes that a fielder deliberately clicked his fingers to create a false edge, several sanctions may be available under recreational cricket disciplinary procedures.

Formal Warning or Reprimand

A disciplinary panel could record an official warning, particularly if it considered the incident isolated and at the lower end of misconduct.

Financial Penalty

Recreational cricket regulations can allow fines and administrative costs, depending on the rules adopted by the league and the classification of the offense.

Playing Suspension

A confirmed attempt to deceive an umpire could result in a ban for a specified number of matches or weeks. The length would depend on the seriousness of the conduct, whether it happened more than once and whether the player had any previous disciplinary record.

League Points Deduction

If the panel determines that the misconduct involved wider team participation or materially affected competition integrity, Saltburn could face a points deduction.

That would be particularly significant because the club was reported to be leading Division Two by 17 points when the controversy emerged.

Alteration of the Match Result

Competition authorities may have powers to adjust points or alter a result in serious cases. This would require a separate assessment of the applicable league rules and the effect of the alleged misconduct.

Expulsion in an Extreme Case

Some recreational cricket disciplinary frameworks allow a participant to be expelled from a league for sufficiently serious or repeated misconduct. This would ordinarily sit at the most severe end of possible sanctions.

The authorities may also consider aggravating factors, including whether the alleged action was planned, repeated, supported by teammates or previously used in other matches.

Recent cricket cases show that authorities usually distinguish between an isolated breach and wider leadership or cultural failure. That principle also appeared in The Sports Encounter’s coverage of the disciplinary questions surrounding Ben Stokes and England’s leadership.

Could Other Players Be Punished?

Potentially, but only if evidence establishes their involvement.

Unbelievable. Clicky Ponting must be the biggest cheat in cricket history. How long has he been doing this? How many batsmen’s days has he ruined? https://t.co/XptHEfE9uo
— Piers Morgan (@piersmorgan) July 28, 2026

A wicketkeeper or another fielder should not automatically be punished merely for appealing. Cricket teams regularly appeal together when close-in fielders believe they have heard an edge.

The disciplinary question would concern what each player knew and intended.

Investigators may examine:

Whether teammates knew a fake sound would be created
Whether the tactic had been discussed before the match
Whether similar incidents occurred previously
Whether players continued appealing despite knowing there was no edge
Whether team officials or captains became aware of the conduct
Whether relevant footage or other evidence was removed or withheld

Claims about similar incidents have appeared in media coverage, but they remain allegations. Each incident would require separate evidence and proper review.

Responsibility may also extend beyond the individual if investigators find evidence of coordination. A captain or club official cannot be held accountable merely because the player belonged to the team. Authorities would need evidence showing knowledge, encouragement or a failure to act after becoming aware of the conduct.

What Has the League Said?

The North Yorkshire and South Durham Cricket League confirmed that it received a formal complaint and started a full investigation.

Its statement said:

“The league have received a formal complaint regarding alleged incidents in a division two game on Saturday 25 July 2026. A full investigation has been initiated and until such time as the formal processes are complete no further comment will be made.”

That restrained response is appropriate. Viral footage can generate immediate public judgment, but disciplinary authorities must review the complete video, hear from the umpires, speak to the players and allow those accused to respond.

The investigation may also need to determine whether the finger movement visible in the footage produced the sound heard, whether the timing was intentional and whether it influenced the umpire.

Questions involving player conduct, governing-body rules and public judgment require careful handling. A similar need for evidence and proportionate judgment appeared when The Sports Encounter examined how Ben Stokes’ conduct affected England’s leadership culture and public trust.

Why Amateur Cricket Depends So Heavily on Player Honesty

Professional cricket can review close decisions through multiple camera angles, stump microphones, ball-tracking systems and edge-detection technology.

Club cricket operates in a different environment.

An amateur umpire may work alone at one end without access to replay technology. Camera footage, if it exists, may be recorded for streaming or coaching rather than formal decision reviews. Players therefore carry a greater responsibility to preserve the integrity of the contest.

This does not mean players should withdraw every close appeal or correct every decision that benefits them. Honest disagreements will always exist.

The line is crossed when a participant intentionally manufactures the evidence that prompts the decision.

Recreational sport survives because competitors generally accept that winning has limits. Once deception becomes normalized, leagues must invest more heavily in monitoring, disciplinary systems and technology simply to reproduce the trust players should have protected themselves.

The wider importance of safeguarding standards and clearly defined conduct rules can also be seen in the regulations surrounding teenage cricketer Vaibhav Sooryavanshi and senior dressing rooms. Different situations involve different risks, but both demonstrate why sporting rules depend on participants respecting their purpose.

Final Verdict: A Small Action With a Serious Meaning

The alleged finger click lasted less than a second. Its possible significance stretches much further.

Cricket permits tactical deception in limited forms. A bowler can disguise a slower ball. A batter can use an unexpected shot. A captain may position a fielder to encourage a false stroke.

Those actions test an opponent’s cricketing judgment.

Creating a fake edge sound would serve a different purpose. It would attempt to convince an umpire that an event occurred when it did not.

If the allegation is proven, the conduct would constitute a clear challenge to fair play, respect for match officials and the integrity of recreational cricket. A suspension would be a realistic possibility, while stronger sanctions could follow if investigators find evidence of repetition, planning or wider team involvement.

For now, the distinction between allegation and fact remains essential.

The video has created serious questions. The North Yorkshire and South Durham Cricket League must now determine whether “Clicky Ponting” was an unfortunate visual coincidence, an isolated act of misconduct or evidence of a deliberate method used to manufacture wickets.

Frequently Asked Questions

What did the cricketer allegedly do?

A close-in fielder is accused of clicking his fingers as the ball passed the batter’s bat. The allegation is that the sound imitated a faint edge and contributed to the umpire giving the batter out caught behind.

Is clicking your fingers illegal in cricket?

Clicking your fingers is not automatically an offense. It may become unfair play if a fielder does it deliberately to distract or deceive a batter or umpire during a delivery.

Which cricket law could apply?

MCC Law 41 addresses unfair play, including deliberate attempts by fielders to distract, deceive or obstruct batters.

Could the dismissal be cancelled?

An umpire can correct a decision promptly during a match under certain circumstances. Changing a dismissal after the match has ended would depend on the league’s regulations and disciplinary powers.

What punishment could the player receive?

Possible sanctions may include a reprimand, fine, playing suspension or another disciplinary penalty. More serious consequences, including a points deduction, could be considered if investigators establish repeated conduct or wider team involvement.