Pakistan Women started off the super six stage on a losing note as Sri Lanka Women defeated them by five wickets at the Nondescripts Cricket Club Ground in Colombo on Wednesday.
Despite brilliant 64 and 63-run knocks by Nahida Khan and Javeria Khan respectively, the Women in Green were unable to stop a rampant Sri Lanka side that was propelled by Eshani Kaushalya’s 65-run blitz that included eight boundaries.
Electing to field first, Sri Lanka Women were given a target of 213. Pakistan lost opener Ayesha Zafar early on in the match but a 119-run stand between Nahida and Javeria put Pakistan in a strong position. Bismah Maroof and Nain Abidi contributed with 20 and 17 runs respectively, while captain Sana Mir made 17 to ensure Pakistan reach the 212-run mark and post a defendable total.
Inoka Ranaweera and Chamari Kumarihami were the pick of the bowlers for Sri Lanka as they claimed two wickets for 33 and 34 runs respectively at impressive economy rates of 4.12 and 3.40 respectively.
In reply, Sri Lanka Women reached the target with 2.2 overs and five wickets to spare.
The Islanders were given a strong start courtesy a 75-run opening stand between Nipuni Hansika and Chamari Atapattu who made 37 and 35 runs respectively. Hansika’s innings included five fours, while Atapattu’s comprised of six.
Following the dismissals of the two in the 16th and 18th over respectively, wicketkeeper Prasadani Weerakkody (45) and Kaushalya took the reins and registered an 88-run partnership to make Sri Lanka’s win all but imminent.
For Pakistan, Nashra Sandhu, who carried on her sublime form in the qualifiers, and Ghulam Fatima claimed two wickets apiece for 37 and 28 runs respectively.
In other matches, India Women defeated South Africa by 49 runs, while Bangladesh defeated Ireland by seven wickets.
Pakistan now face Ireland in the next match on February 17.
The top four teams in the super six stage will qualify for the 2017 ICC Women’s World Cup.
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ