Safety, Stanford, 2024–⁠26

Charlie Eckhardt

Number
No. 39
Height
6′2″
Weight
205 lb
Class (2026)
Sophomore
Hometown
Centennial, CO

Charlie Eckhardt plays safety for Stanford. Last time out, against Elon: 2 tackles.

2026 so far

26 tackles, 1 INT

Last game: 2 tackles vs. Elon, W 34–⁠7

Next game: vs. NC State, Oct 23

Game by game this season, tackles
  1. 2HAW
  2. 9MIA
  3. 5GT
  4. 6@WAKE
  5. 2@ND
  6. 2ELON

Filled bars: wins; outlined: losses.

Career highs

9tackles, career highvs. Miami, 2026

Defense

Tackles, season by season, with his team’s record

* The season in progress, so far.

SeasonTeamTklSoloTFLSacksIntPDHur
2025Stanford342220031
2026Stanford261400100
Career603620131

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

SeasonTeamNo.PosClassHtWt
2024Stanford39SRS
2025Stanford39SFr.
2026Stanford39SSo.6′2″205

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 6 games, 26 tackles, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Aug 29vs.Hawai’iW 37–⁠27210000
Sep 4vs.MiamiL 6–⁠45960010
Sep 26vs.Georgia TechW 34–⁠27520000
Oct 3atWake ForestL 3–⁠57640000
Oct 10atNotre DameL 7–⁠58200000
Oct 17vs.ElonW 34–⁠7210000
2025 Stanford 10 games, 34 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Sep 13vs.Boston CollegeW 30–⁠20220000
Sep 20atVirginiaL 20–⁠48630000
Sep 27vs.San José StateW 30–⁠29640001
Oct 11atSMUL 10–⁠34100000
Oct 18vs.Florida StateW 20–⁠13410001
Oct 25atMiamiL 7–⁠42530000
Nov 1vs.PittsburghL 20–⁠35650000
Nov 8atNorth CarolinaL 15–⁠20220001
Nov 22vs.CaliforniaW 31–⁠10111000
Nov 29vs.Notre DameL 20–⁠49111000

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.