Currently at Corsham
| Season | Runs | Innings | Not OutsN.O. | Centuries100s | Average | 
|---|---|---|---|---|---|
| 2023 | 8 | 2 | 1 | 0 | 8.00 | 
| 2024 | 70 | 2 | 0 | 0 | 35.00 | 
| Total | 78 | 4 | 1 | 0 | 26.00 | 
| Team | Runs | Innings | Not OutsN.O. | Centuries100s | Average | 
|---|---|---|---|---|---|
| Corsham 4 | 78 | 4 | 1 | 0 | 26.00 | 
| Total | 78 | 4 | 1 | 0 | 26.00 | 
| Season & Team | Runs | Innings | Not OutsN.O. | Centuries100s | Average | 
|---|---|---|---|---|---|
| 2023 Corsham 4 | 8 | 2 | 1 | 0 | 8.00 | 
| 2024 Corsham 4 | 70 | 2 | 0 | 0 | 35.00 | 
| Total | 78 | 4 | 1 | 0 | 26.00 | 
| Home/Away | Runs | Innings | Not OutsN.O. | Centuries100s | Average | 
|---|---|---|---|---|---|
| Home | 7 | 1 | 1 | 0 | |
| Away | 71 | 3 | 0 | 0 | 23.67 | 
| Total | 78 | 4 | 1 | 0 | 26.00 | 
| Result | Runs | Innings | Not OutsN.O. | Centuries100s | Average | 
|---|---|---|---|---|---|
| Won | 51 | 1 | 0 | 0 | 51.00 | 
| Lost | 27 | 3 | 1 | 0 | 13.50 | 
| Total | 78 | 4 | 1 | 0 | 26.00 | 
| Batting Position | Runs | Innings | Not OutsN.O. | Centuries100s | Average | 
|---|---|---|---|---|---|
| 4 | 71 | 3 | 0 | 0 | 23.67 | 
| 10 | 7 | 1 | 1 | 0 | |
| Total | 78 | 4 | 1 | 0 | 26.00 | 
| Mode of DismissalHow Out | Runs | Innings | Not OutsN.O. | Centuries100s | Average | 
|---|---|---|---|---|---|
| Not Out | 7 | 1 | 1 | 0 | |
| Bowled | 1 | 1 | 0 | 0 | 1.00 | 
| LBW | 51 | 1 | 0 | 0 | 51.00 | 
| Caught Fielder | 19 | 1 | 0 | 0 | 19.00 | 
| Total | 78 | 4 | 1 | 0 | 26.00 | 
Less ...
More ...
| Date | Match | Pos | Score | How Out | Bowling | Hattrick? | 
|---|---|---|---|---|---|---|
| 12 Aug 2023 | Allington 2 v Corsham 4 | 4 | 1 | Bowled | No | |
| 02 Sep 2023 | Corsham 4 v Melksham 3 | 10 | 7 | Not Out | No | |
| 03 Aug 2024 | Swindon 5 v Corsham 4 | 4 | 51 | LBW | No | |
| 17 Aug 2024 | Lacock 2 v Corsham 4 | 4 | 19 | Caught Fielder | No | |
| 03 May 2025 | Swindon Titans 2 v Corsham 4 | 7 | Did Not Bat | No | 
No fielding dismissals
No matches umpired
Hide ...
Show ...
If any of the above information is incorrect, click here for information on how to get it corrected.