Defensive end, Stony Brook, 2022–25
Franco Milano
- Number
- No. 96
- Height
- 6′3″
- Weight
- 270 lb
- Class (2025)
- Senior
- Hometown
- Brewster, NY
Franco Milano played defensive end at Stony Brook (2022–25).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | Int | PD | Hur |
|---|---|---|---|---|---|---|---|---|
| 2023 | Stony Brook | 1 | 0 | 0 | 0 | 0 | 0 | 0 |
| 2024 | Stony Brook | – | – | – | – | 1 | – | – |
| 2025 | Stony Brook | 5 | 3 | 0.5 | 0 | 0 | 0 | 0 |
| Career | 6 | 3 | 0.5 | 0 | 1 | 0 | 0 | |
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
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | Stony Brook | 96 | DE | Fr. | ||
| 2023 | Stony Brook | 96 | DE | So. | ||
| 2024 | Stony Brook | 96 | DE | Jr. | ||
| 2025 | Stony Brook | 96 | DE | Sr. | 6′3″ | 270 |
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
2025 Stony Brook 1 game, 5 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 28 | at San Diego State | L 0–42 | 5 | 3 | 0.5 | 0 | 0 | 0 |
2024 Stony Brook 1 game, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Oct 26 | vs. William & Mary | W 35–13 | – | – | – | – | 1 | – |
2023 Stony Brook 1 game, 1 tackle
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 16 | at Arkansas State | L 7–31 | 1 | 0 | 0 | 0 | 0 | 0 |
No box score in the source for Oct 7 at Morgan State, so that game is 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.