Yorkshire CCC v Hampshire - Hampshire triumph in Scarborough

YORKSHIRE today fell to their third defeat in four County Championship games.
By YP Sport
Published 25th Jul 2022, 10:47 GMT
Updated 28th Jul 2022, 15:10 GMT
IN TROUBLE: Yorkshire's Adam Lyth is bowled by Hampshire's Mohammad Abbas. Picture by Allan McKenzie/SWpix.comIN TROUBLE: Yorkshire's Adam Lyth is bowled by Hampshire's Mohammad Abbas. Picture by Allan McKenzie/SWpix.com
IN TROUBLE: Yorkshire's Adam Lyth is bowled by Hampshire's Mohammad Abbas. Picture by Allan McKenzie/SWpix.com

The hosts went down by seven wickets against Hampshire in Scarborough.

Victory was sealed at 3.06pm when James Vince hit the winning runs.

Hide Ad
Hide Ad

It means Yorkshire will go into their final block of four games in September looking over their shoulder.

Yorkshire CCC are back at North Marine Road, Scarborough this week, facing Hampshire in the County Championship. Picture by Will Palmer/SWpix.comYorkshire CCC are back at North Marine Road, Scarborough this week, facing Hampshire in the County Championship. Picture by Will Palmer/SWpix.com
Yorkshire CCC are back at North Marine Road, Scarborough this week, facing Hampshire in the County Championship. Picture by Will Palmer/SWpix.com

Hampshire reached their target of 214 in comfortable style, openers Felix Organ (72) and Ian Holland (71) sharing a stand of 135.

The visitors lost three wickets for 12 runs in six overs shortly after lunch to briefly raise the home side’s hopes.

Holland steered Ben Coad to Tom Kohler-Cadmore at first slip, Organ pulled a short ball from Dom Bess to Matty Revis at deep mid-wicket, and Joe Weatherley was lbw to Coad for a 14-ball duck.

But James Vince (43) and Nick Gubbins (20) got the job done as Hampshire strengthened their title ambitions.

Related topics:HampshireYorkshire CCCJames VinceYorkshire

Comment Guidelines

National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.