Scotland vs UAE: Third-Place Scorecard and 45-Run Win Explained

Scotland beat the United Arab Emirates by 45 runs in the Hong Kong Sixes third-place match on 1 November 2026. The organiser's structured result feed lists Scotland at 135/1 and UAE at 90/3, with both innings lasting six overs. This guide explains the score, the placing and a numerical mistake in the prose summary.

Checked on 2 November 2026, this is a completed-match explainer, not a live scorecard. It distinguishes figures published by different official resources and uses original exercises to show how a result can be checked. Historical photographs illustrate cricket and regional context; they do not claim to show the match or its participants in the 2026 event.

What was the Scotland versus UAE result?

Scotland won the Cup division's third-place playoff, securing third place rather than the main championship. The organiser's result feed records 135 against 90 and a 45-run victory. Those totals agree with the arithmetic: subtracting UAE's 90 from Scotland's 135 gives 45, not 46.

Keep the division and placing beside the result when sharing it. A third-place playoff is a meaningful match with its own outcome, but its winner is not the Cup champion. A card that crops away the words “third place” can turn an accurate celebration into a misleading statement about the tournament.

The date and edition are equally important. The same national sides can meet in a different format or year, so a search for their names alone may return another match. Here the event is the 2026 Hong Kong Sixes, and the relevant fixture occurred on finals day, 1 November.

For a first notebook entry, write four labels before adding any numbers: event, stage, date and teams. Then add the two totals and the result. This order makes the information easier to verify because a reader can identify the match before deciding what the score means.

Why does one report mention a different run margin?

The organiser's finals-day prose describes the same totals but uses 46 in its margin wording. Its structured result feed instead says Scotland won by 45 runs, which matches 135 minus 90. This guide uses the reconciled 45-run figure and identifies the inconsistency rather than copying both numbers without explanation.

The likely source of confusion is the difference between a winning target and a winning margin. In a straightforward chase of a completed 135, the target would be 136. A final 90 is 46 short of that target, while the defending side's winning margin is 135 minus 90, or 45.

Those are different questions. “How many more runs would have reached the target?” and “By how many runs did the first side win?” do not have to produce the same number. A one-run gap between them is expected in the simple example, because equalling the first total is not the same as exceeding it.

Try the distinction with invented totals of 100 and 80. The first side wins by twenty runs; the second side would have needed twenty-one more to reach 101. Writing the question beside each calculation prevents a correct subtraction from being given the wrong sporting label.

How should you handle the wicket-count difference?

The organiser's structured feed lists Scotland at 135/1. A broadcaster's summary displays 135/0. Both show the same run totals and a 45-run result. Without a definitive reconciled ball-by-ball record, it would be wrong to pretend that the differing wicket fields have been independently settled here.

That does not prevent reporting the supported winner and margin. It means the disputed field should remain attributed. A compact scorecard can say “organiser feed: 135/1” and keep the note nearby. If an authoritative corrected record becomes available, that field can be updated with its source.

This is a useful lesson in field-level verification. Two sources do not have to agree on every detail before you can identify what they do agree on. Separate the confirmed result, the conflicting wicket count and the unresolved reason for the difference. Avoid letting one uncertain field make every other fact appear equally uncertain.

A practical worksheet can mark fields as corroborated, attributed or unresolved. Do not turn those labels into fake numerical confidence scores. Their purpose is to explain the evidence plainly. A reader should understand which claim is supported and what additional record would be needed to resolve the remaining question.

What do six overs represent here?

The structured feed supplies thirty-six legal balls for each innings and six balls per over. Six times six equals thirty-six. This makes the innings length clear without assuming that a six-a-side event must use the same allocation as a standard T20 international or an older edition of the tournament.

Competition names and formats can mislead when readers rely on memory. Sixes refers to the event's distinctive format; it is not permission to copy every rule from another competition with six in its name. Use this edition's actual records and conditions for questions about its innings structure.

For a small original exercise, draw thirty-six empty boxes in six rows. Each box represents a legal delivery, not every recorded event. You can then mark scoring outcomes in the boxes while keeping extras or other actions in a separate note. This avoids confusing the event log's length with the legal-ball allocation.

The drawing also makes remaining deliveries easy to see. If twenty-four legal balls have been used, twelve remain in the model. You do not need to treat a displayed over string as a decimal. Count the legal balls first, then convert the display if you want a compact scoreboard.

Historical UAE cricket infrastructure in 2007; not the match venue or its current construction status.

How do the two innings rates compare?

Using the feed's six completed overs, Scotland's 135 corresponds to 22.5 runs per over and UAE's 90 to fifteen. These are simple descriptions of the listed innings totals and length. They are not career rates, predictions or an assessment of every shot played during either innings.

An average rate does not mean each over contained that exact number of runs. Six different over totals can add to 135 in many ways. A bar chart of the innings would require actual over-by-over data; the final total alone cannot supply it. Do not invent six bars simply to make the page look more interactive.

Use fictional values to see why. An innings of sixty from six overs could consist of ten in each over, or a mixture of quiet and expensive overs. Both have an average of ten. The same summary can hide different patterns, so a question about acceleration needs a sequence rather than just the final average.

This is a transferable data lesson. Before building a graph, ask whether the source contains the observations the graph claims to show. A final score supports a total and a derived average. It does not support a delivery map, a shot chart or a detailed momentum line without additional data.

What do the highlighted batting contributions tell us?

The organiser's prose highlights Michael Leask's quick half-century and Jack Jarvis's contribution in Scotland's innings. Those highlights help identify important batting involvement, but they are not a complete scorecard. A full team total also depends on other contributions and extras, as recorded by the appropriate scoring source.

Do not use a short highlight paragraph to infer every batter's dismissal status or time at the crease. A report may focus on its most notable performances and omit other fields. That selection is normal in a summary, but it means the reader must use a fuller record for questions the paragraph does not answer.

For a fictional practice table, enter two highlighted scores, one other batting contribution and an extras column. Add them to the team total. Then remove one column and ask whether the remaining values are sufficient to reconstruct the innings. This shows why a partial summary should not be treated as a complete accounting.

The exercise is especially helpful when two players remain unbeaten in a short event. Their individual scores do not automatically tell you the innings' wicket count or the rules governing retirement and return. Keep the scorecard fields separate instead of deriving a rule from an attractive highlight line.

How did third place fit into the tournament?

The official fixture structure placed the two Cup semi-final losers in a third-versus-fourth playoff. Scotland and UAE therefore met after missing the Cup final, with their placing still to decide. That route explains why an earlier defeat did not mean either side had no further match in the event.

Draw a bracket with separate lines for the championship final and the placing game. A semi-final winner moves to the first; a semi-final loser can move to the second under this event's structure. The labels prevent a learner from assuming every knockout defeat immediately ends all participation.

That structure is competition-specific. Other tournaments may have no third-place fixture, or they may use different classification games. A familiar bracket should not be imposed on every event. First read the organiser's route, then build your diagram around it rather than filling a template with assumptions.

Our Hong Kong Sixes final guide covers the separate championship outcome. Keeping that question separate from this playoff preserves the achievement of third place without rewriting it as a title win. A clear archive gives each completed fixture its proper role.

Build a scorecard with an evidence note

Use named fields for team, runs, wickets, legal balls, stage and result. Keep the source link beside the record, and allow a note on a disputed field. A well-designed card does not need a dramatic warning across the whole page; it needs a precise explanation attached to the number that differs.

Test the margin calculation independently from the target calculation. With these totals, one should show 45 and the other a target of 136 in the straightforward model. If both cells are labelled “margin,” the problem is the heading even when the subtraction itself is correct. Units and questions are part of the calculation.

Then test how the card behaves when wickets are unresolved. It should preserve the attributed value and note, not replace the field with a guessed zero. This is a useful project in our programming courses, where missing information can be represented explicitly instead of being disguised as a result.

Before sharing the card, ask another reader to identify the winner, placing and margin without help. They should also see that the wicket detail is attributed rather than independently reconciled. If those distinctions survive a quick reading, the card is doing more than displaying numbers: it is teaching accurate result reading.

A final arithmetic check

Use three invented defending totals and chase totals of your own. For each, calculate the run margin and then the remaining runs needed to exceed the defending total. Explain why the two answers differ by one in the simple completed-innings model. Do not substitute a rain-adjusted target or an unfinished match into that exercise without changing its assumptions.

This method helps you spot a common reporting slip without becoming careless in the other direction. A numerical mismatch is a reason to inspect the labels, not an invitation to declare every source unreliable. Correct the narrow point the evidence supports and preserve what is already well established about the match.

As a final exercise, explain the result to someone using only a pencil and the two totals. First calculate the defending margin, then write the ordinary winning threshold separately. Ask which answer belongs in a headline and which describes what the chase still needed. If your listener can identify both without confusing them, the explanation has worked. The skill is not remembering forty-five; it is knowing why that number answers the result question while another nearby number answers a different one.

Sources

• Hong Kong Sixes: organiser's result feed, record 5529, for the attributed innings fields and 45-run result.
• Organiser's finals-day account, for third-place context and the noted margin wording.
• FanCode: completed event results, for corroboration of the winner and margin, while displaying a different Scotland wicket count.

Keep the source date alongside your notes so that a later update can be compared with the same clearly identified record.

Image credits: cover: John Lord, source, CC BY-SA 2.0. Resized and converted to WebP. inline: Imre Solt, source, CC BY-SA 3.0. Resized and converted to WebP.