Reading a partnership
In cricket, runs are scored in partnerships. Two batters at the crease together build a stand, and the quality of those stands decides most innings. A scorecard gives you raw runs and balls, but the interesting story lives in the derived numbers: how fast the pair scored, who was the aggressor, how reliant they were on boundaries, and how much of the team total they shouldered. This tool turns a few scorecard figures into that fuller picture.
How it works
From the two batters’ runs and balls the tool computes the combined totals, then derives several rates:
partnership runs = b1 runs + b2 runs
total balls = b1 balls + b2 balls
run rate = runs / (total balls / 6)
strike rate = batter runs / batter balls * 100
balls per boundary = total balls / (fours + sixes)
% of team total = partnership runs / team total * 100Run rate is expressed per over, the natural unit in cricket, by dividing balls by six. Strike rate is computed individually so you can see which batter set the tempo. Balls per boundary captures the scoring style, and the optional team total reveals how central the stand was to the innings.
Tips and interpretation
The most revealing comparison is the two strike rates. A partnership of 100 might be built by one batter racing along at a strike rate of 160 while the other anchors at 90, a classic accelerator-and-rotator pairing that lets the team attack without collapsing. Balls per boundary then tells you the risk profile: a stand scoring a boundary every five balls is hitting through the line and trusting timing, while one going eight or nine balls between boundaries is rotating strike and accumulating safely. Finally, watch the percentage of team total. When a single partnership accounts for well over half the innings, the rest of the order has failed, and a side that lives on one big stand per game is more fragile than its totals suggest. Use these figures together to judge not just how many runs came, but how and from whom.