Defensive back, Miami, 2007–11
Lee Chambers
- Number
- No. 32
- Height
- 5′10″
- Hometown
- Coffeeville, MS
Lee Chambers played defensive back at Miami (2007–11).
Rushing
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
Defense before 2016
| Season | G | Solo | Ast | Tkl | PBU |
|---|---|---|---|---|---|
| 2009 | 7 | 3 | 1 | 4 | 0 |
| 2010 | 2 | 1 | 1 | 2 | 0 |
| 2011 | 6 | 11 | 4 | 15 | 1 |
| On file | 15 | 6 | 21 | 1 | |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in). A dash: the source has no number for it.
On the roster
As each season’s roster listed the player (CollegeFootballData). Classes before the latest listing are counted back from it; “Yr 1” is the year on file where that count can’t place a season he played (a redshirt, transfer or 2020 year); height and weight as last listed.
Game by game
2009 Miami 6 games, 153 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 7 | at Florida State | W 38–34 | 5 | 10 | 0 | 4 | – | – |
| Sep 17 | vs. Georgia Tech | W 33–17 | 2 | 12 | 0 | 8 | – | – |
| Oct 10 | vs. Florida A&M | W 48–16 | 16 | 38 | 1 | 12 | – | – |
| Oct 17 | at UCF | W 27–7 | 3 | 15 | 0 | 7 | – | – |
| Nov 7 | vs. Virginia | W 52–17 | 10 | 67 | 0 | 20 | 1 | 8 |
| Nov 28 | at South Florida | W 31–10 | 6 | 11 | 0 | 9 | – | – |
2008 Miami 3 games, 116 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 28 | vs. Charleston Southern | W 52–7 | 5 | 25 | 0 | 6 | – | – |
| Oct 11 | vs.UCF | W 20–14 | 4 | 31 | 0 | 25 | – | – |
| Dec 27 ✦ | vs. California | L 17–24 | 9 | 60 | 0 | 18 | 1 | 4 |
Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.
Is this you, or do you know of something wrong or missing here? Suggest a correction. We check each one against a source before changing the page.