Defensive end, Rice (from Colgate), 2018–23
Coleman Coco
- Number
- No. 44
- Height
- 6′5″
- Weight
- 264 lb
- Class (2023)
- Senior
- Hometown
- Pittsburgh, PA
Coleman Coco played defensive end at Colgate (2018–22) and Rice (2023).
Career highs
8tackles, career highvs. East Carolina, 2023Defense
Season lines from CollegeFootballData, regular season and bowls.
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
2023 Rice 11 games, 37 tackles, 1.5 sacks
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 16 | vs. Texas Southern | W 59–7 | 1 | 1 | 0 | 0 | 0 |
| Sep 23 | at South Florida | L 29–42 | 3 | 0 | 0.5 | 0 | 0 |
| Sep 30 | vs. East Carolina | W 24–17 | 8 | 3 | 1.5 | 0 | 0 |
| Oct 7 | vs. UConn | L 31–38 | 1 | 0 | 0 | 0 | 0 |
| Oct 19 | at Tulsa | W 42–10 | 7 | 3 | 0.5 | 0.5 | 0 |
| Oct 28 | vs. Tulane | L 28–30 | 1 | 1 | 0 | 0 | 0 |
| Nov 4 | vs. SMU | L 31–36 | 4 | 1 | 0 | 0 | 0 |
| Nov 11 | at UTSA | L 14–34 | 2 | 0 | 0 | 0 | 0 |
| Nov 18 | at Charlotte | W 28–7 | 3 | 1 | 0.5 | 0 | 0 |
| Nov 25 | vs. Florida Atlantic | W 24–21 | 4 | 2 | 2 | 1 | 0 |
| Dec 26 ✦ | vs. Texas State | L 21–45 | 3 | 1 | 1.5 | 0 | 0 |
2022 Colgate 2 games, 7 tackles
2019 Colgate 1 game, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | at Air Force | L 7–48 | 3 | 0 | 0 | 0 | 0 |
No box score in the source for Aug 24 vs. Villanova; Sep 14 at William & Mary; Sep 21 vs. Maine; Sep 28 at Dartmouth; Oct 5 vs. Lehigh; Oct 12 vs. Bucknell; Oct 19 at Cornell; Oct 26 at Holy Cross; Nov 2 at Georgetown; Nov 9 vs. Fordham; Nov 16 at Lafayette, 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.