Linebacker, Richmond, 2022–25
Owen Laughlin
- Number
- No. 43
- Height
- 6′1″
- Weight
- 220 lb
- Class (2025)
- Senior
- Hometown
- Shrewsbury, NJ
Owen Laughlin played linebacker at Richmond (2022–25).
Team titles: Coastal Athletic Association champions, 2023 and 2024
Rushing
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2024 | Richmond | 1 | 0 | 0 | 0 | 0 | 0 |
Returns
| Season | Team | KR | Yds | TD |
|---|---|---|---|---|
| 2023 | Richmond | 1 | 8 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | Richmond | 43 | LB | Fr. | ||
| 2023 | Richmond | 43 | LB | So. | ||
| 2024 | Richmond | 43 | LB | Jr. | ||
| 2025 | Richmond | 43 | LB | Sr. | 6′1″ | 220 |
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 Richmond 1 game, 4 rushing yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Tkl | Sacks | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 13 | at North Carolina | L 6–41 | 1 | 4 | 0 | – | – | – |
2024 Richmond 1 game, 1 tackle
| Date | Opponent | Result | Car | Rush yds | Rush TD | Tkl | Sacks | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 31 | at Virginia | L 13–34 | – | – | – | 1 | 0 | 0 |
2023 Richmond 4 games, 1 return, 8 yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Tkl | Sacks | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 9 | at Michigan State | L 14–45 | 1 | 20 | 0 | – | – | – |
| Sep 30 | vs. Hampton | L 14–31 | – | – | – | – | – | – |
| Oct 28 | vs. Campbell | W 44–13 | 1 | 9 | 0 | – | – | – |
| Nov 25 ✦ | vs. North Carolina Central | W 49–27 | 1 | 2 | 0 | – | – | – |
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.