Mike Pethick
Currently at Wanborough
Batting Stats
By Season
2018 |
76 |
4 |
0 |
0 |
19.00 |
2019 |
5 |
4 |
0 |
0 |
1.25 |
Total |
81 |
8 |
0 |
0 |
10.12 |
By Team
Wanborough |
81 |
8 |
0 |
0 |
10.12 |
Total |
81 |
8 |
0 |
0 |
10.12 |
By Season & Team
2018 Wanborough |
76 |
4 |
0 |
0 |
19.00 |
2019 Wanborough |
5 |
4 |
0 |
0 |
1.25 |
Total |
81 |
8 |
0 |
0 |
10.12 |
By Home/Away
Home |
36 |
3 |
0 |
0 |
12.00 |
Away |
45 |
5 |
0 |
0 |
9.00 |
Total |
81 |
8 |
0 |
0 |
10.12 |
By Result
Won |
80 |
7 |
0 |
0 |
11.43 |
Lost |
1 |
1 |
0 |
0 |
1.00 |
Total |
81 |
8 |
0 |
0 |
10.12 |
By Batting Position
3 |
4 |
1 |
0 |
0 |
4.00 |
5 |
73 |
5 |
0 |
0 |
14.60 |
6 |
4 |
2 |
0 |
0 |
2.00 |
Total |
81 |
8 |
0 |
0 |
10.12 |
By Mode of DismissalHow Out
Bowled |
5 |
2 |
0 |
0 |
2.50 |
LBW |
4 |
2 |
0 |
0 |
2.00 |
Caught Keeper |
1 |
1 |
0 |
0 |
1.00 |
Caught Fielder |
71 |
3 |
0 |
0 |
23.67 |
Total |
81 |
8 |
0 |
0 |
10.12 |
Less ...
More ...
Match Data
Matches Played
30 Jun 2018 |
Collingbourne v Wanborough |
3 |
4 |
Bowled |
|
No |
14 Jul 2018 |
Wanborough v Biddestone 3 |
5 |
34 |
Caught Fielder |
|
No |
21 Jul 2018 |
Royal Wootton Bassett 3 v Wanborough |
5 |
34 |
Caught Fielder |
|
No |
04 Aug 2018 |
Bathford v Wanborough |
5 |
4 |
LBW |
|
No |
11 Aug 2018 |
Westbury 2 v Wanborough |
6 |
|
Did Not Bat |
|
No |
04 May 2019 |
Melksham v Wanborough |
6 |
3 |
Caught Fielder |
|
No |
11 May 2019 |
Wanborough v Ramsbury |
6 |
1 |
Bowled |
|
No |
25 May 2019 |
Marlborough 2 v Wanborough |
5 |
0 |
LBW |
|
No |
01 Jun 2019 |
Wanborough v Nationwide House 2 |
5 |
1 |
Caught Keeper |
|
No |
Fielding Dismissals
21 Jul 2018 |
Royal Wootton Bassett 3 v Wanborough |
Caught Fielder |
Ashwin Dias |
Imran Hanif |
10 |
11 May 2019 |
Wanborough v Ramsbury |
Stumped |
Jervis Noronha |
Dave Smith |
9 |
11 May 2019 |
Wanborough v Ramsbury |
Stumped |
Liam Stacey |
Frederick Walker |
50 |
11 May 2019 |
Wanborough v Ramsbury |
Stumped |
Liam Stacey |
Alex Knight |
0 |
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.