Linebacker, Holy Cross, 2017–18
Ryan Brady
- Number
- No. 44
- Height
- 6′1″
- Weight
- 223 lb
- Hometown
- Chicago, IL
Ryan Brady played linebacker at Holy Cross (2017–18).
Career highs
15tackles, career highat Boston College, 2018Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2017 | Holy Cross | 14 | 8 | 1.5 | 0 | 0 | 0 |
| 2018 | Holy Cross | 15 | 3 | 3 | 0 | 0 | 0 |
| Career | 29 | 11 | 4.5 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2017 | Holy Cross | 44 | LB | ||
| 2018 | Holy Cross | 44 | LB | 6′1″ | 223 |
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
2018 Holy Cross 1 game, 15 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 8 | at Boston College | L 14–62 | 15 | 3 | 3 | 0 | 0 |
No box score in the source for Sep 1 at Colgate; Sep 15 vs. Yale; Sep 22 vs. Dartmouth; Sep 29 vs. Bucknell; Oct 6 at New Hampshire; Oct 12 at Harvard; Oct 27 vs. Lehigh; Nov 3 at Lafayette; Nov 10 vs. Fordham; Nov 17 at Georgetown, so those games are not listed.
2017 Holy Cross 1 game, 14 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | at UConn | L 20–27 | 14 | 8 | 1.5 | 0 | 0 |
No box score in the source for Sep 9 at Bucknell; Sep 16 vs. New Hampshire; Sep 23 at Dartmouth; Sep 30 vs. Lafayette; Oct 7 vs. Monmouth; Oct 14 at Yale; Oct 21 vs. Colgate; Oct 28 vs. Georgetown; Nov 4 at Fordham; Nov 11 at Lehigh, 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.