Toby Robertson
Currently at Ramsbury
Batting Stats
By Season
| 2022 |
62 |
3 |
0 |
0 |
20.67 |
| Total |
62 |
3 |
0 |
0 |
20.67 |
By Team
| Ramsbury |
62 |
3 |
0 |
0 |
20.67 |
| Total |
62 |
3 |
0 |
0 |
20.67 |
By Season & Team
| 2022 Ramsbury |
62 |
3 |
0 |
0 |
20.67 |
| Total |
62 |
3 |
0 |
0 |
20.67 |
By Home/Away
| Home |
62 |
3 |
0 |
0 |
20.67 |
| Total |
62 |
3 |
0 |
0 |
20.67 |
By Result
| Lost |
10 |
2 |
0 |
0 |
5.00 |
| No Result |
52 |
1 |
0 |
0 |
52.00 |
| Total |
62 |
3 |
0 |
0 |
20.67 |
By Batting Position
| 2 |
7 |
1 |
0 |
0 |
7.00 |
| 5 |
55 |
2 |
0 |
0 |
27.50 |
| Total |
62 |
3 |
0 |
0 |
20.67 |
By Mode of DismissalHow Out
| LBW |
52 |
1 |
0 |
0 |
52.00 |
| Caught Keeper |
3 |
1 |
0 |
0 |
3.00 |
| Caught Fielder |
7 |
1 |
0 |
0 |
7.00 |
| Total |
62 |
3 |
0 |
0 |
20.67 |
Less ...
More ...
Bowling Stats
By Season
| 2022 |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
| Total |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
By Team
| Ramsbury |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
| Total |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
By Season & TeamS/T
| 2022 Ramsbury |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
| Total |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
By Home/AwayH/A
| Home |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
| Total |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
By Result
| Lost |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
| Total |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
By Bowling PositionPos
| 3 |
1 |
2 |
0 |
9-1-35-2 |
17.50 |
27.00 |
3.89 |
| 5 |
1 |
0 |
0 |
2-1-1-0 |
|
|
0.50 |
| Total |
2 |
2 |
0 |
11-2-36-2 |
18.00 |
33.00 |
3.27 |
Less ...
More ...
Match Data
Matches Played
| 02 Jul 2022 |
Ramsbury v Spye Park |
5 |
52 |
LBW |
|
No |
| 09 Jul 2022 |
Ramsbury v Heytesbury & Sutton Veny |
2 |
7 |
Caught Fielder |
2.0-1-1-0 |
No |
| 23 Jul 2022 |
Ramsbury v Keevil |
5 |
3 |
Caught Keeper |
9.0-1-35-2 |
No |
Fielding Dismissals
No fielding dismissals
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.
