Jasdeep Singh
Currently at Swindon NALGO
Batting Stats
By Season
| 2019 |
20 |
4 |
0 |
0 |
5.00 |
| 2023 |
0 |
3 |
2 |
0 |
0.00 |
| Total |
20 |
7 |
2 |
0 |
4.00 |
By Team
| Swindon NALGO |
0 |
1 |
0 |
0 |
0.00 |
| Swindon NALGO 2 |
20 |
6 |
2 |
0 |
5.00 |
| Total |
20 |
7 |
2 |
0 |
4.00 |
By Season & Team
| 2019 Swindon NALGO 2 |
20 |
4 |
0 |
0 |
5.00 |
| 2023 Swindon NALGO |
0 |
1 |
0 |
0 |
0.00 |
| 2023 Swindon NALGO 2 |
0 |
2 |
2 |
0 |
|
| Total |
20 |
7 |
2 |
0 |
4.00 |
By Home/Away
| Home |
19 |
4 |
1 |
0 |
6.33 |
| Away |
1 |
3 |
1 |
0 |
0.50 |
| Total |
20 |
7 |
2 |
0 |
4.00 |
By Result
| Won |
16 |
4 |
2 |
0 |
8.00 |
| Lost |
4 |
3 |
0 |
0 |
1.33 |
| Total |
20 |
7 |
2 |
0 |
4.00 |
By Batting Position
| 2 |
11 |
2 |
0 |
0 |
5.50 |
| 6 |
3 |
1 |
0 |
0 |
3.00 |
| 7 |
6 |
3 |
1 |
0 |
3.00 |
| 9 |
0 |
1 |
1 |
0 |
|
| Total |
20 |
7 |
2 |
0 |
4.00 |
By Mode of DismissalHow Out
| Not Out |
0 |
2 |
2 |
0 |
|
| Bowled |
1 |
2 |
0 |
0 |
0.50 |
| LBW |
10 |
1 |
0 |
0 |
10.00 |
| Caught Keeper |
6 |
1 |
0 |
0 |
6.00 |
| Caught Fielder |
3 |
1 |
0 |
0 |
3.00 |
| Total |
20 |
7 |
2 |
0 |
4.00 |
Less ...
More ...
Match Data
Matches Played
| 04 May 2019 |
Swindon NALGO 2 v Royal Wootton Bassett 3 |
2 |
10 |
LBW |
|
No |
| 11 May 2019 |
Burbage & Easton Royal 3 v Swindon NALGO 2 |
2 |
1 |
Bowled |
|
No |
| 01 Jun 2019 |
Swindon NALGO 2 v Blunsdon |
6 |
3 |
Caught Fielder |
|
No |
| 15 Jun 2019 |
Malmesbury 2 v Swindon NALGO 2 |
8 |
|
Did Not Bat |
|
No |
| 27 Jul 2019 |
Swindon NALGO 2 v Beckington 2 |
7 |
6 |
Caught Keeper |
|
No |
| 03 Jun 2023 |
Swindon NALGO 2 v Ramsbury |
9 |
0 |
Not Out |
|
No |
| 29 Jul 2023 |
Marlborough v Swindon NALGO |
7 |
0 |
Bowled |
|
No |
| 26 Aug 2023 |
Swindon NALGO 2 v Wroughton Wranglers |
10 |
|
Did Not Bat |
|
No |
| 02 Sep 2023 |
Wilcot v Swindon NALGO 2 |
7 |
0 |
Not Out |
|
No |
Fielding Dismissals
| 29 Jul 2023 |
Marlborough v Swindon NALGO |
Caught Keeper |
Ahmed Hassan |
James Richardson |
13 |
Matches Umpired
No matches umpired
Hide ...
Show ...
If any of the above information is incorrect, click here for information on how to get it corrected.
