← All runs

AWG Final - ND Vs Para 2025 Jan 25

AW Green Shield (U16) · scorecard · video · Players — bowling & batting

← Back to the over

Why 3.3 — near end

A Rebase to R Aparajit : No Run

The scorer tapped
04:12:40.00
always after the ball, by an inconsistent margin
The code says
—
it found nothing
You say
—
not marked
This over offered
4
1 got through the gates
Every candidate, and what became of it

In the order the gates are applied. The first one a candidate fails is the reason it is not here.

candidate at 15081.82 seconds
04:11:22.47 15,082.47s ✗ wrong colours for the fielding side crossing inferred from the follow-through
speed 1.84 m/s
approach 0.0 m
carried on 8.4 m
side of the stumps -1.15 m
blob 58 px
field gathered 1
candidate at 15290.8 seconds
04:14:51.45 15,291.45s chosen crossing inferred from the follow-through
speed 2.24 m/s
approach 0.0 m
carried on 12.5 m
side of the stumps -1.87 m
blob 61 px
field gathered 0
candidate at 15295.56 seconds
04:14:56.21 15,296.21s ✗ wrong colours for the fielding side crossing inferred from the follow-through
speed 6.50 m/s
approach 0.0 m
carried on 6.1 m
side of the stumps -1.86 m
blob 43 px
field gathered 0
candidate at 15311.68 seconds
04:15:12.33 15,312.33s ✗ wrong end
speed 3.45 m/s
approach 1.4 m
carried on 2.0 m
side of the stumps 1.26 m
blob 290 px
field gathered 1
Merges at this end

The moment the bowler becomes one blob with the umpire and the non-striker. It peaks 0.39s before he crosses, so the ball is gone about a second later. Used only where a crossing could not be found — it needs no track, which is the point of it.

04:10:48.54 surge 2.5× over the recent quiet 294 px
04:11:06.44 surge 3.1× over the recent quiet 366 px
04:11:28.04 surge 2.6× over the recent quiet 312 px
04:12:15.84 surge 2.5× over the recent quiet 296 px
04:12:48.24 surge 2.8× over the recent quiet 338 px