Defensive back, Grambling, 2018–22
Ryan Fields
- Number
- No. 21
- Height
- 6′2″
- Weight
- 190 lb
- Class (2022)
- Senior
- Hometown
- Cypress, TX
Ryan Fields played defensive back at Grambling (2018–22).
Defense
Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.
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
2022 Grambling 2 games, 5 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | at Arkansas State | L 3–58 | 5 | 4 | 0 | 0 | 0 | 0 |
| Nov 5 | vs. Arkansas–Pine Bluff | W 36–10 | – | – | – | – | 1 | – |
No box score in the source for Sep 17 at Jackson State, so that game is not listed.
2021 Grambling 2 games, 5 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 11 | at Southern Miss | L 0–37 | 2 | 2 | 1 | 0 | 0 | 1 |
| Sep 18 | at Houston | L 0–45 | 3 | 3 | 0 | 0 | 0 | 0 |
No box score in the source for Sep 5 vs. Tennessee State; Sep 25 at Prairie View A&M; Oct 30 at Florida A&M, so those games are not listed.
2019 Grambling 1 game, 4 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 31 | at UL Monroe | L 9–31 | 4 | 2 | 0 | 0 | 0 | 0 |
No box score in the source for Sep 21 at Alabama State; Sep 28 at Prairie View A&M; Oct 5 at Jackson State; Oct 12 vs. Alabama A&M; Oct 26 at Arkansas–Pine Bluff; Nov 2 vs. Texas Southern; Nov 9 vs. Alcorn State; Nov 16 at Mississippi Valley State; Nov 30 vs. Southern, so those games are not listed.
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.