Cornerback, Stanford, 2024–26
Cam Richardson
- Number
- No. 8
- Height
- 6′2″
- Weight
- 190 lb
- Class (2026)
- Junior
- Hometown
- Irvington, NJ
Cam Richardson plays cornerback for Stanford. Last time out, at Wake Forest: 2 tackles.
2026 so far
11 tackles
Last game: 2 tackles at Wake Forest, L 3–57
Next game: vs. NC State, Oct 23
Filled bars: wins; outlined: losses.
Defense
* The season in progress, so far.
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
2026 Stanford 5 games, 11 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 29 | vs. Hawai’i | W 37–27 | 3 | 3 | 0 | 0 | 0 |
| Sep 4 | vs. Miami | L 6–45 | 2 | 1 | 0 | 0 | 0 |
| Sep 19 | at Duke | L 7–35 | 3 | 1 | 0 | 0 | 0 |
| Sep 26 | vs. Georgia Tech | W 34–27 | 1 | 1 | 0 | 0 | 1 |
| Oct 3 | at Wake Forest | L 3–57 | 2 | 1 | 0 | 0 | 0 |
2025 Stanford 5 games, 9 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 23 | atHawai’i | L 20–23 | 1 | 0 | 0 | 0 | 0 |
| Sep 6 | at BYU | L 3–27 | 2 | 2 | 0 | 0 | 0 |
| Sep 13 | vs. Boston College | W 30–20 | 3 | 2 | 0 | 0 | 0 |
| Sep 20 | at Virginia | L 20–48 | 1 | 0 | 0 | 0 | 0 |
| Oct 25 | atMiami | L 7–42 | 2 | 2 | 0 | 0 | 0 |
2024 Stanford 5 games, 13 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 7 | vs. Cal Poly | W 41–7 | 1 | 0 | 0 | 0 | 0 |
| Oct 12 | at Notre Dame | L 7–49 | 1 | 0 | 0 | 0 | 0 |
| Oct 19 | vs. SMU | L 10–40 | 6 | 5 | 0 | 0 | 0 |
| Nov 2 | at NC State | L 28–59 | 3 | 1 | 0 | 0 | 0 |
| Nov 29 | at San José State | L 31–34 | 2 | 1 | 0 | 0 | 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.