Defensive back, Bryant, 2022–26
Olatunde Mkparu
- Number
- No. 3
- Height
- 6′1″
- Weight
- 210 lb
- Class (2026)
- Senior
Olatunde Mkparu plays defensive back for Bryant. Last time out, at Maine: 7 tackles.
2026 so far
42 tackles, 1 INT
Last game: 7 tackles at Maine, W 17–14
Next game: vs. Stony Brook, Oct 24
Filled bars: wins; outlined: losses.
Career highs
9tackles, career highat Hampton, 2026Defense
* The season in progress, so far.
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 | Bryant | 3 | DB | RS | ||
| 2023 | Bryant | 3 | DB | Fr. | ||
| 2024 | Bryant | 3 | DB | So. | ||
| 2025 | Bryant | 3 | DB | Jr. | ||
| 2026 | Bryant | 3 | DB | Sr. | 6′1″ | 210 |
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
2026 Bryant 7 games, 42 tackles, 1 INT
2025 Bryant 4 games, 6 tackles, 2 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | at | L 3–19 | 2 | 2 | 0 | 0 | 0 | 1 |
| Sep 6 | at | W 27–26 | 4 | 2 | 0 | 0 | 0 | 0 |
| Oct 25 | at | L 17–38 | – | – | – | – | 1 | – |
| Nov 1 | vs. | L 7–35 | – | – | – | – | 1 | – |
2024 Bryant 1 game, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Oct 12 | vs. | L 17–24 | – | – | – | – | 1 | – |
2023 Bryant 1 game, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Nov 11 | at | W 38–3 | – | – | – | – | 1 | – |
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.
