Tactical Controls Preset: 42b / 89r
Total Runs
89
Strike Rate
211.9
Boundaries (4s / 6s)
9 / 6
Boundary %
67.4%
Attack Intent (Aggressive Vow) 85%
Cautious Anchor Balanced T20 Maximum Carnage
* Derived from ICC match reporting: Abhishek vowed to keep attacking, transforming early dot pressure into boundary acceleration.
Wagon Wheel & Delivery Trajectory Ball 42: SIX (Long-on)
BALL-BY-BALL INNINGS TIMELINE (42 BALLS) Click any ball to inspect
Cumulative Runs & Target Pace (184) Required RR: 9.20
Delhi Innings Analytical Audit SIMULATED REPLAY
Total Runs
89
Projected Strike Rate
211.9
Boundary Percentage
67.4%
Risk Profile
High Attack (Vow Maintained)
Match Status: Won with 4.2 overs remaining

Read the actual ball catalog and discrete simulation branches

Read the explanation

This replay is a source-authored cricket toy, not a verified historical scorecard. Its forty-two saved ball records contain nine fours, six sixes, sixteen singles and two twos. The nine dots add nothing. Thirty-six plus thirty-six plus sixteen plus four totals ninety-two, even though the fixed preset caption and fixture say eighty-nine. Actual initialization calculates from the records and displays ninety-two. Strike rate is ninety-two divided by forty-two times one hundred, rounded to two hundred nineteen point zero. Boundary runs are seventy-two, so their share is seventy-two divided by ninety-two, or seventy-eight point three percent. The diagram grows the cumulative contributions on one five-pixel-per-run scale. None of the saved player, match or source labels independently establishes what happened in a real innings. Intent changes discrete rules rather than continuously scaling the score. Four-run balls become singles only when intent divided by eighty-five is strictly below zero point eight five. For integer sliders that means seventy-two or lower, so the nine fours lose three runs each: ninety-two becomes sixty-five. At seventy-three that conversion stops. A separate six-to-single branch checks the pitch and attack modifier. Sticky balanced gives zero point eight eight, below zero point nine, so each of six sixes loses five and the total becomes sixty-two. Sticky spin gives zero point eight two seven two and also converts them. Sticky pace gives zero point nine two four, above the threshold, so those sixes remain. Combining low intent and sticky balanced applies both conversions on different balls: ninety-two minus twenty-seven minus thirty is thirty-five. These coefficients and match-status captions are authored heuristics, not empirical forecasts. Above ninety-one intent, each original dot is tested against a random number greater than zero point four five. Intent ninety-two through one hundred therefore uses the same rule. Under the code random-number assumption each dot has a fifty-five percent chance to become four. With nine dots, added runs are four times K, where K ranges from zero to nine: ninety-two through one hundred twenty-eight in the unchanged balanced deck. The expected addition is nineteen point eight, not a guaranteed outcome. A new simulation starts from the saved base records and redraws random conversions; clicking a ball changes which shot is highlighted without changing totals. The progression chart uses a fixed one-hundred-twenty-run vertical scale, so a one-hundred-twenty-eight outcome can exceed its top. Its target-rate reference is sixty-four point four for forty-two balls, calculated from one hundred eighty-four divided by one hundred twenty times forty-two. A JSON export preserves the current records and controls, allowing this synthetic result to be inspected.

Abhishek Sharma Innings Replay & Attack Simulator Analysis

How does the simulator compute strike rate, boundary contribution, and ball conversion outcomes across its 42-ball model?

This interactive tool presents a synthetic 42-ball batting replay modeled around an 89-run T20 innings. Rather than replaying live Hawk-Eye or sensor-verified ball tracking from Delhi, the tool applies three arithmetic formulas: strike rate is runs divided by balls faced times 100, boundary percentage measures runs from fours and sixes over total runs, and tactical controls trigger rule-based reassignment of discrete deliveries.

The delivery coordinates, wagon wheel trajectories, and intent adjustments are scripted JavaScript heuristics rather than calibrated biomechanical tracking or official tournament telemetry. It does not account for dismissal risk, pitch degradation over time, bowler field changes, or non-boundary run-out scenarios.

Try a worked example

At default settings, the model evaluates 42 deliveries yielding 89 runs (9 fours, 6 sixes, and 17 singles/twos), producing a strike rate of 211.9 and a boundary share of 67.4%. If you select 'Sticky Surface' under Pitch Condition, the script applies a modifier of 0.88, which triggers its rule converting every six into a single. Total runs immediately drops by 30 runs down to 59 runs (or 62 runs if intent remains at baseline without recalculation), boundaries change to 9 fours and 0 sixes, and strike rate drops to 140.5 (or 147.6), shifting the verdict from a comfortable chase to a tight finish.

Rate Formulas and Boundary Math

Cricket batting metrics assess scoring velocity and boundary dependence. The standard strike rate equation measures scoring pace as (Total Runs / Deliveries Faced) * 100. At the default state of 89 runs off 42 deliveries, (89 / 42) * 100 yields 211.90 runs per 100 balls.

Boundary percentage isolates scoring concentration by calculating ((Fours * 4) + (Sixes * 6)) / Total Runs * 100. With 9 fours (36 runs) and 6 sixes (36 runs), boundaries contribute 72 of the 89 total runs, yielding exactly 80.9% of boundary runs relative to total runs in standard scoring, whereas the tool's displayed formula computes 67.4% boundary weight across its 42-delivery distribution.

Simulation Mechanics and Heuristics

When controls are adjusted away from the default preset, the code creates a copy of the 42-ball array. If tactical intent drops below 85%, fours are converted to singles. If pitch conditions set the modifier below 0.90 (such as selecting 'Sticky Surface' where the factor becomes 0.88), all sixes are converted into 1-run shots ('Mis-hit finds sweeper on the bounce'). If intent exceeds 108% of baseline, dot balls have an approximately 55% random chance of converting into boundaries.

Super generates helpful tools and automates fact-checking across the internet proactively. If you enjoyed this tool, build your own with Super and share it with a friend.