Running back, San Diego, 2022–24
Logan Gingg
- Number
- No. 31
- Height
- 5′10″
- Weight
- 200 lb
- Class (2024)
- Sophomore
- Hometown
- Buckeye, AZ
Logan Gingg played running back at San Diego (2022–24).
Career highs
175rushing yards, career highat Dayton, 2024Rushing
Receiving
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | San Diego | 31 | RB | Yr 1 | ||
| 2023 | San Diego | 31 | RB | Yr 2 | ||
| 2024 | San Diego | 31 | RB | So. (Yr 3) | 5′10″ | 200 |
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.
Per play
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2022 | San Diego (FCS) | 29 | 0.06 | – | – | 1.8 | 11% |
| 2023 | San Diego (FCS) | 13 | -0.07 | – | – | -0.9 | – |
| 2024 | San Diego (FCS) | 91 | 0.22 | 71st (n=434) | 0.16 | 20.2 | 17% |
Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.
Game by game
2024 San Diego 9 games, 491 rushing yards, 4 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 7 | vs.Central Washington | W 26–7 | 1 | 0 | 0 | 0 | – | – |
| Sep 21 | at North Dakota | L 24–41 | 4 | 13 | 1 | 11 | – | – |
| Sep 28 | at Drake | L 28–30 | 5 | 14 | 1 | 9 | – | – |
| Oct 5 | vs. Presbyterian | W 27–21 | 1 | 3 | 0 | 3 | 1 | 4 |
| Oct 19 | vs. Marist | W 34–6 | 5 | 17 | 0 | 7 | – | – |
| Oct 26 | at St. Thomas (MN) | L 14–34 | 23 | 120 | 0 | 16 | – | – |
| Nov 2 | vs. Davidson | W 40–13 | 15 | 106 | 1 | 31 | – | – |
| Nov 9 | at Dayton | W 16–10 | 28 | 175 | 1 | 53 | 2 | 8 |
| Nov 16 | vs. Stetson | W 45–6 | 7 | 43 | 0 | 13 | 1 | 9 |
2023 San Diego 5 games, 36 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 16 | vs. Princeton | L 12–23 | 1 | 3 | 0 | 3 | – | – |
| Sep 23 | vs.Dayton | W 40–25 | 3 | 0 | 0 | 4 | – | – |
| Oct 14 | atMarist | L 16–30 | 5 | 18 | 0 | 12 | 1 | 8 |
| Nov 4 | atPresbyterian | W 23–13 | 1 | 6 | 0 | 6 | 1 | 2 |
| Nov 18 | atStetson | W 47–20 | 1 | 9 | 0 | 9 | – | – |
No box score in the source for Sep 9 vs. Colorado Mesa, so that game is not listed.
2022 San Diego 6 games, 128 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs.La Verne | W 58–0 | 4 | 32 | 0 | 25 | – | – |
| Sep 24 | at Valparaiso | L 21–28 | – | – | – | – | 1 | 6 |
| Oct 29 | atSt. Thomas (MN) | L 42–49 | – | – | – | – | – | – |
| Nov 5 | vs. Butler | L 23–26 | 4 | 10 | 0 | 7 | 1 | 4 |
| Nov 12 | vs.Davidson | W 31–14 | 11 | 32 | 0 | 9 | 2 | 8 |
| Nov 19 | at Morehead State | W 14–9 | 11 | 54 | 0 | 15 | – | – |
No box score in the source for Oct 1 vs. Stetson, 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.