PNG Women v Scotland Women: Seven-Wicket Result and Fraser’s All-Round Impact
Read Scotland Women’s seven-wicket win over PNG, Katherine Fraser’s 45 and 3/10, and clear explanations of the target, overs and balls remaining.

Papua New Guinea Women versus Scotland Women: result
Scotland Women beat Papua New Guinea Women by seven wickets in their Women's Emerging Nations Trophy match in Ajman on 12 November 2026. The completed score record shows PNG dismissed for 93 and Scotland reaching 95 for three in 13.1 overs. Katherine Fraser contributed 45 from 29 balls and took three for ten.
Those figures describe the completed match, not a live score that will keep updating on this page. Search results can retain an earlier innings-break snapshot after a game ends. Check the match date and completed status before treating an old target graphic as evidence that the chase is still in progress.
This report explains the result and the arithmetic behind it without inventing a delivery-by-delivery account. It also places the fixture in its women's tournament context. The teams, competition and format matter: this was not a men's match or a score from a previous edition with the same two countries.
The score in a readable form
| Item | Completed-match record |
|---|---|
| Date | 12 November 2026 |
| Match | Papua New Guinea Women v Scotland Women |
| Competition | ICC Women's Emerging Nations Trophy |
| Venue | Seven Districts Ground, Ajman |
| PNG innings | 93 all out in 20 overs |
| Scotland innings | 95/3 in 13.1 overs |
| Result | Scotland won by seven wickets |
| Fraser's contribution | 45 from 29 balls; 3/10 |
The numbers tell a clear result story, but each has its own meaning. The winning margin counts wickets remaining, not the difference between the two totals. The overs notation describes completed overs and additional legal deliveries. Fraser's batting and bowling figures refer to separate contributions and should not be combined into a single statistic.
Why the target was 94, but the final total was 95
To pass a first-innings total of 93 in an ordinary chase, the batting side needs at least 94. The final total can be higher than the minimum because the winning scoring event can add more than the one run required. A target and a final total do not have to be identical.
This arithmetic does not identify the actual final stroke. Without a verified delivery record, it would be wrong to invent a winning boundary or describe a particular batter's shot. The completed totals establish that Scotland passed PNG's score; a detailed account of the winning delivery requires additional evidence.
For new followers, this is a useful distinction between knowing the result and narrating the action. A scorecard supports some conclusions directly. Other descriptions, however plausible, need commentary or footage. Good match writing should not disguise the second category as though it were visible in the first.
Understanding the seven-wicket margin
Scotland lost three wickets while completing the chase. In the usual ten-wicket innings structure, that leaves seven, which gives the stated margin. It does not mean that Scotland scored seven more runs, won seven separate contests or dismissed seven PNG batters with a particular type of bowling.
A chasing win is normally expressed by wickets remaining, while a successful defence is normally expressed by runs. That difference can confuse readers who expect every result to use the same unit. Identify which side batted second before interpreting the margin.
The margin is useful but incomplete as a description of the performance. Time used, wickets lost and the target all contribute context. A seven-wicket win chasing a small total and the same margin chasing a very large one do not represent identical tasks. Read the total alongside the result rather than treating the margin as a complete story.
Why 13.1 overs is not 13.1 in decimal arithmetic
Cricket's over notation separates completed overs from extra legal deliveries. Here, 13.1 means 13 complete six-ball overs plus one ball: 79 legal deliveries. It does not mean 13 overs plus one tenth of an over. That distinction is essential when calculating scoring rates or the number of balls remaining.
A full 20-over allocation contains 120 legal deliveries. Subtracting the 79 used in Scotland's chase leaves 41 unused. This is a calculation from the completed score, not a separate claim about a special tournament rule or a bonus awarded for finishing early.
Try another example as a learning exercise: 14.4 overs means 88 balls, not 86.4 or 14.4 balls. Convert overs to legal deliveries first, perform the arithmetic and only then express a rate. This small habit prevents many errors in score summaries and spreadsheet analyses.
What Fraser's two contributions tell us
Fraser's 45 from 29 balls represents a substantial part of Scotland's completed total. Her three wickets for ten runs also identify a significant bowling contribution. Describing both is more informative than reducing the match to one headline about either the chase or the collapse.
However, the figures do not by themselves reveal every technical detail. They cannot establish the exact field for each delivery, the intent behind each stroke or the conversation between players. Those details should not be invented to make a scorecard-based report sound like an eyewitness account.
The broader cricket lesson is that an all-round contribution can shape both halves of a game. Restricting an opponent and helping complete the chase are separate tasks. A player who contributes to both gives a team more than one route to influence the result, even though each discipline still deserves its own analysis.

Illustrative cricket equipment, not a photograph of the ball used in the PNG–Scotland match.
Calculating the batting strike rate
Strike rate expresses runs per 100 balls. Fraser's reported 45 from 29 gives 45 divided by 29, multiplied by 100, or approximately 155.17. That describes her scoring rate in this innings. It is not a career figure, a guarantee of future scoring or a measure of how every delivery was played.
PNG's innings provides a different team calculation. Ninety-three runs across 20 overs gives a scoring rate of 4.65 runs per over. Scotland's rate should be calculated using 79 legal balls, rather than treating 13.1 as an ordinary decimal. Ninety-five runs across those balls corresponds to approximately 7.22 runs per over.
These are derived calculations included to help readers understand the score. They do not replace the official record. When building a spreadsheet, retain the original runs and balls so that another person can reproduce the result instead of seeing only an unexplained rounded number.
Tournament context without predicting the final
Durham's pre-tournament information identified Scotland's opening fixture against PNG and placed Scotland alongside Sri Lanka, Ireland, PNG and the UAE in Group A. That establishes the wider setting for the result. It does not mean that one opening win alone decides the competition or guarantees qualification for a later stage.
Early results create a position from which a team continues, rather than a final judgement on every participant. A win can be encouraging while further matches remain important. A defeat can require improvement without proving that a team has nothing left to contribute.
For updated group positions, consult the official tournament page and check the matches included in the table. This article does not publish a provisional standing as though it were the final ranking, and it does not add points or a net-run-rate figure without verifying the relevant competition calculation.
Why net run rate should not be improvised
Net run rate looks simple when described as a scoring-rate comparison, but competition calculations include details that matter, particularly for all-out innings and interrupted games. A person should not take one match's two displayed rates and automatically label their difference the current official tournament net run rate.
The safe approach is to distinguish your own illustrative arithmetic from the published standings. If you calculate a rate to understand this chase, label it as a calculation from this match. If you report the official table, use the competition's published value and date.
This distinction is useful in close qualification races, where an incorrect number can mislead supporters about what a team needs next. It is better to leave an unverified calculation out than to present a confident figure that uses the wrong treatment of overs or combines matches inconsistently.
What PNG can take from the score, and what needs more evidence
The completed total indicates that PNG did not set a large target in this match. A coach reviewing the performance would reasonably examine where runs and wickets were lost. The score alone, however, cannot identify whether a particular technical problem, tactical choice or playing condition caused the outcome.
That is why a useful review would consult the innings sequence and footage before assigning blame. It might separate the early overs, middle period and finish, then ask how each phase affected the next. Those are analytical questions, not claims that this article has reviewed every ball.
Supporters can apply the same standard. A disappointing result should not lead to invented personal criticism or a declaration that a player's whole career has been decided. Identify the evidence, ask a focused cricket question and allow the next performance to contribute new information.
Following women's cricket with the right context
The simplest way to avoid a wrong score is to check the full team name, competition, date and venue. PNG and Scotland have met in different settings. A search for the country names alone can return men's fixtures, older women's matches or a live page whose headline has not caught up with the final result.
Use official tournament and team information for the schedule, then a completed score record for the result. If two pages disagree, inspect their timestamps and match identifiers before choosing the more dramatic claim. An old match with a similar title is not confirmation of today's result.
This also helps new supporters discover the competition rather than seeing each match as an isolated search trend. Following a group's fixtures and completed results provides a more coherent view of how teams respond over the tournament. It gives emerging players room to be understood through repeated performances.
Questions about the match
Who won PNG Women versus Scotland Women on 12 November?
Scotland won by seven wickets. PNG made 93 all out, and Scotland finished on 95 for three in 13.1 overs. These are completed-match figures, not an updating live score. Check the date if another search result still shows an innings break or an unfinished chase.
How many balls did Scotland have left?
The chase used 79 legal deliveries, leaving 41 from a full 120-ball allocation. The conversion matters because 13.1 overs means 13 overs and one ball. Treating it as a decimal number produces the wrong answer and can also distort a run-rate calculation.
What did Katherine Fraser contribute?
The completed record gives Fraser 45 from 29 deliveries and bowling figures of three for ten. Those contributions belong to this match. They should not be described as her career average or extended into an invented delivery-by-delivery account without consulting the relevant commentary or footage.
Does the result decide the tournament?
No. It is an opening group-stage result within a larger competition. Later fixtures and the applicable progression rules still matter. For current standings, use the official tournament table and check which completed matches it includes rather than treating one win as a guarantee of the final outcome.
A better way to share the result
Include the full women's team names, the date and the two totals when sending a summary to a friend. That makes the message useful even if it is read after the live-score page has changed. Add the margin, but do not replace the actual result with a vague description such as “easy win” that hides the supporting numbers.
For more dated cricket and learning guides, browse the RayTech article collection. This match offers a straightforward result and a useful chance to practise reading scores correctly: distinguish target from total, wickets from runs and overs notation from decimal arithmetic. Those habits make following the next match easier, regardless of which team you support.
When checking a wicket figure, also distinguish wickets credited to a bowler from all dismissals in an innings. A team can lose wickets through different dismissal modes, so a bowling table is not simply a complete list of every player who was out. That distinction is useful when reconciling an innings total with several individual bowling analyses. Keep the original scorecard available so that your arithmetic can be checked against the actual record rather than a shortened graphic.
Sources
- Source: Completed match result and score record
- Source: Durham's Scotland squad and tournament preview
- Source: ICC tournament fixtures and results
Image credits: cover: Grange Cricket Ground by kim traynor, source, CC BY-SA 2.0. Resized and converted to WebP. inline: WhiteTailedEagle, source, CC0. Resized and converted to WebP.
Found an error or an outdated detail? Report a correction with the article URL and original source.
