Abhishek Sharma Delhi Landmark Century Innings Analyzer

Balls To Century

Record 100 Milestone

Boundary Percentage

71.15%

74 runs from 4s & 6s

Boundary Runs

8 Fours + 7 Sixes

Running Runs

1s, 2s & 3s rotated

Century Reached

Yes

104 Runs in 48 Balls

Export Status

Ready

JSON & Text Available

Tactical Aggression Deck

Live Engine

Batting Aggression & Strike Rate 216.7 SR

Boundary Frequency Weight 71.2%

Powerplay Aggression Bias (Overs 1-6) 1.25x

Innings Timeline Scrubber Over 8.0 (Completed)

Over 1 (Powerplay) Over 4 Over 8 (Century 104)

Over-by-Over Scoring Velocity vs Cumulative Progression 100 Run Century Threshold Marked

Arun Jaitley Stadium Wagons & Trajectory Distribution 8 Fours · 7 Sixes (74 Runs)

Fours (Flat Drives & Cuts)

Sixes (Aerial Dispatches)

Milestone Telemetry & Phase Distribution

Powerplay (Overs 1-6)

52 Runs

Blistering 14.2 rpo run velocity taking early charge in Delhi

Middle Overs (Overs 7-16)

52 Runs

Maintained extreme strike rotation to cross 100 in 46 balls

Death Overs (Overs 17-20)

0 Runs (Sub-10 Over Century)

Record reached prior to death overs; no death phase required

Landmark Speed

46 Balls to 100

Highest scoring velocity for an Indian opener in landmark matches

Match Provenance & Verified Innings Report Card

Source Grounding: Modeled directly from the verified ICC broadcast feature commemorating Abhishek Sharma's record-setting Delhi century (ICC Match Status 2100649856167759899). Calculations calibrated to 104 runs from 48 balls, 8 fours, 7 sixes, 46 balls to century, 52 powerplay runs, and 52 middle overs runs.

T20 Innings Pacing, Boundary Distribution, and Strike Acceleration Mechanics

How do boundary hit rates and over-by-over strike acceleration dictate milestone progression in limited-overs cricket modeling?

In limited-overs cricket, a batter's scoring velocity combines discrete running between wickets with four- and six-run boundary strikes. This simulator lets learners explore counterfactual pacing scenarios by adjusting batting aggression (strike rate), boundary frequency weighting, and powerplay bias across an 8-over sequence modeled after an aggressive top-order milestone knock.

The 104 runs off 48 balls scenario set at Arun Jaitley Stadium in Delhi functions as a stylized tactical benchmark rather than an official international scorecard. The over-by-over run allocations and 15 radial wagon-wheel vectors are deterministic mathematical fixtures designed for interactive pacing analysis rather than ball-by-ball optical tracking data.

Try a worked example

Click the 'Anchor Pacing' button (#presetConserve). The engine adjusts the strike rate slider to 160.0 SR and the boundary frequency weight to 52.0%. The recalculation scales total runs from 104 down to 77 across the 48 balls faced, computing 6 fours (24 runs) and 3 sixes (18 runs). This changes Boundary Runs to 42, shifts Running Runs to 35, adjusts the Boundary Percentage to 54.55%, and toggles 'Century Reached' to 'No' while displaying 'N/A (Did not cross 100)' for Balls to Century.

Boundary Scoring Laws vs Strike Rotation

Cricket scoring accumulates runs through two distinct physical mechanisms: physical running between wickets governed by Law 18 and boundary awards governed by Law 19 of the Laws of Cricket. Under Law 19, a stroke that reaches or crosses the boundary perimeter on the bounce awards four runs, whereas an aerial strike that clears the boundary on the full yields six runs. Laws of Cricket - Wikipedia

In modern T20 power-hitting analyses, boundary percentage (the proportion of total runs scored exclusively from boundaries) serves as a primary indicator of scoring velocity. When boundary percentages rise above 70%, batters minimize delivery consumption while sharply elevating the team's run rate through powerplay fielding restrictions. Laws of Cricket - Wikipedia

Counterfactual Innings Simulation Mechanics

The interactive engine scales baseline runs using an aggression factor proportional to the target strike rate divided by the baseline strike rate of 216.67. When custom parameters are selected, the model reapportions runs between sixes and fours using a calibrated ratio, recomputing boundary run contributions, running singles, and phase splits across the powerplay and middle overs.

Sources and further reading

Laws of Cricket - Wikipedia
Defines Law 18 (Scoring runs) and Law 19 (Boundaries) including four runs for a boundary along the ground and six runs for an aerial boundary clearing the boundary edge.

Boundary arithmetic, over totals, and the scrubber limits

Your browser does not support video.

Read the explanation

This saved cricket lab contains an unverified match fixture and a toy simulation. The video explains its arithmetic, not independently confirmed innings records or measured shot trajectories. Baseline eight fours give thirty two runs, and seven sixes give forty two. Together those boundaries contribute seventy four of the stored one hundred four runs. The remaining thirty runs are classified as running runs. Seventy four divided by one hundred four is about seventy one point one five percent. The diagram grows from the four contribution to all boundary runs, then to the total, on a shared scale. Baseline is explicitly locked to these literals; touching a simulation slider switches to a different calculation path. Boundary Surge sets aggression to two hundred fifty, boundary weight eighty five percent, and powerplay bias one point five. Total runs round one hundred four times two hundred fifty over two hundred sixteen point six seven, giving one hundred twenty. Boundary rounding produces fourteen fours and eight sixes, or one hundred four boundary runs, leaving sixteen running runs. But overs use a separate formula: each baseline over is multiplied by the aggression factor, and the first six also by powerplay bias. The eight resulting over totals are twenty one, twenty eight, fourteen, twenty four, three, zero, twenty five, and thirty five. They sum to one hundred fifty, thirty more than the reported total. The diagram compares total and over sum on the same scale. This is a source inconsistency, not a valid simulated scorecard. The timeline scrubber selects the cumulative score from the over array. In baseline, overs one, six, seven and eight give twelve, fifty two, seventy four and one hundred four. The cumulative bar shows those values. Scrubbing does not recompute the full-innings boundary counts: eight fours and seven sixes stay displayed. The wagon wheel draws from only fifteen stored vectors, at most eight fours and seven sixes. Surge asks for fourteen and eight, but the drawing cannot show all twenty two requested boundaries. Offline, native canvas fallback still draws the cumulative line and wagon wheel; Chart and Matter enhancements are untested. JSON and text exports preserve the current source calculations, including their inconsistencies. Inspect those exported values rather than treating the report title as validation.