Run out: which batter is out and which runs count?
Understand a broken wicket, the batter's ground and why the unfinished run is not added.
The ground and wicket are linked
MCC Law 38 concerns a batter out of their ground while the ball is in play and the wicket is fairly broken by a fielder's action, subject to the exceptions in the Law. A run does not have to be attempted for every run-out situation.
The batter dismissed is the one whose ground is at the end where the wicket is broken. The player closest to the camera or the batter who played the shot is not automatically the one out.
A no-ball does not remove every risk
Run out can apply even when no-ball has been called, but the Law contains specified exceptions. Do not reduce a no-ball to a promise that no dismissal is possible. Nor should every wicket broken by the wicketkeeper be labelled run out without checking the circumstances.
In a hypothetical attempted second run after one was completed, the run in progress when a run-out occurs is not scored. Runs already completed stand, together with applicable penalties, subject to the Law's specific cases.
Read the score and dismissal separately
A wicket and the team's running total can change in the same sequence. That is not necessarily a contradictory scorecard. The bowler's wicket figure and the team wicket count also need not rise together for this dismissal.
Use ScoreZaap's final event label and updated score rather than an assumed extra run. This guide explains the general scoring effect, not a decision about a named close replay or a non-striker leaving early.