L Richards
Currently at Spye Park
Batting Stats
By Season
| Season | Runs | Innings | Not OutsN.O. | Centuries100s | Average |
|---|---|---|---|---|---|
| 2025 | 3 | 1 | 0 | 0 | 3.00 |
| 2026 | 21 | 1 | 0 | 0 | 21.00 |
| Total | 24 | 2 | 0 | 0 | 12.00 |
By Team
| Team | Runs | Innings | Not OutsN.O. | Centuries100s | Average |
|---|---|---|---|---|---|
| Spye Park | 3 | 1 | 0 | 0 | 3.00 |
| Spye Park 2 | 21 | 1 | 0 | 0 | 21.00 |
| Total | 24 | 2 | 0 | 0 | 12.00 |
By Season & Team
| Season & Team | Runs | Innings | Not OutsN.O. | Centuries100s | Average |
|---|---|---|---|---|---|
| 2025 Spye Park | 3 | 1 | 0 | 0 | 3.00 |
| 2026 Spye Park 2 | 21 | 1 | 0 | 0 | 21.00 |
| Total | 24 | 2 | 0 | 0 | 12.00 |
By Home/Away
| Home/Away | Runs | Innings | Not OutsN.O. | Centuries100s | Average |
|---|---|---|---|---|---|
| Away | 24 | 2 | 0 | 0 | 12.00 |
| Total | 24 | 2 | 0 | 0 | 12.00 |
By Result
| Result | Runs | Innings | Not OutsN.O. | Centuries100s | Average |
|---|---|---|---|---|---|
| Lost | 3 | 1 | 0 | 0 | 3.00 |
| No Result | 21 | 1 | 0 | 0 | 21.00 |
| Total | 24 | 2 | 0 | 0 | 12.00 |
By Batting Position
| Batting Position | Runs | Innings | Not OutsN.O. | Centuries100s | Average |
|---|---|---|---|---|---|
| 6 | 3 | 1 | 0 | 0 | 3.00 |
| 10 | 21 | 1 | 0 | 0 | 21.00 |
| Total | 24 | 2 | 0 | 0 | 12.00 |
By Mode of DismissalHow Out
| Mode of DismissalHow Out | Runs | Innings | Not OutsN.O. | Centuries100s | Average |
|---|---|---|---|---|---|
| Bowled | 3 | 1 | 0 | 0 | 3.00 |
| Caught Fielder | 21 | 1 | 0 | 0 | 21.00 |
| Total | 24 | 2 | 0 | 0 | 12.00 |
Less ...
More ...
Match Data
Matches Played
| Date | Match | Pos | Score | How Out | Bowling | Hattrick? |
|---|---|---|---|---|---|---|
| 10 May 2025 | Shrivenham v Spye Park | 6 | 3 | Bowled | No | |
| 02 May 2026 | Swindon 5 v Spye Park 2 | 10 | 21 | Caught Fielder | No | |
| 16 May 2026 | Beckington 2 v Spye Park 2 | 9 | Did Not Bat | 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.