Running back, Colorado, 2021–25
Charlie Offerdahl
- Number
- No. 44
- Height
- 5′11″
- Weight
- 190 lb
- Class (2025)
- Senior
- Hometown
- Littleton, CO
Charlie Offerdahl played running back at Colorado (2021–25).
Rushing
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2021 | Colorado | 44 | RB | RS | ||
| 2022 | Colorado | 44 | RB | Fr. | ||
| 2023 | Colorado | 44 | RB | So. | ||
| 2024 | Colorado | 44 | RB | Jr. | ||
| 2025 | Colorado | 44 | RB | Sr. | 5′11″ | 190 |
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 | Adj. rush |
|---|---|---|---|---|---|---|---|---|
| 2022 | Colorado | 39 | 0.11 | – | – | 4.4 | 8% | 0.02 |
| 2023 | Colorado | 2 | 0.48 | – | – | 1.0 | – | – |
| 2024 | Colorado | 30 | 0.20 | – | – | 6.0 | 7% | – |
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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.
Game by game
2024 Colorado 8 games, 119 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 29 | vs. North Dakota State | W 31–26 | 5 | 15 | 0 | 5 | 2 | 13 |
| Sep 7 | at Nebraska | L 10–28 | 4 | 4 | 0 | 6 | – | – |
| Sep 14 | at Colorado State | W 28–9 | 2 | 16 | 0 | 12 | 1 | −1 |
| Sep 21 | vs. Baylor | W 38–31 | – | – | – | – | – | – |
| Sep 28 | at UCF | W 48–21 | 3 | 11 | 0 | 4 | – | – |
| Oct 19 | at Arizona | W 34–7 | 7 | 53 | 0 | 39 | – | – |
| Nov 16 | vs. Utah | W 49–24 | 1 | 4 | 1 | 4 | – | – |
| Nov 29 | vs. Oklahoma State | W 52–0 | 4 | 16 | 0 | 11 | 1 | 1 |
2023 Colorado 3 games, 11 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 9 | vs.Nebraska | W 36–14 | 2 | 11 | 0 | 6 | – | – |
| Oct 28 | at UCLA | L 16–28 | – | – | – | – | – | – |
| Nov 17 | at Washington State | L 14–56 | – | – | – | – | – | – |
2022 Colorado 10 games, 150 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 2 | vs. TCU | L 13–38 | 1 | 6 | 0 | 6 | – | – |
| Sep 10 | at Air Force | L 10–41 | 1 | 5 | 0 | 5 | – | – |
| Sep 17 | at Minnesota | L 7–49 | 8 | 55 | 0 | 14 | – | – |
| Sep 24 | vs.UCLA | L 17–45 | 14 | 47 | 0 | 10 | – | – |
| Oct 1 | atArizona | L 20–43 | 3 | 18 | 0 | 7 | 1 | 36 |
| Oct 22 | at Oregon State | L 9–42 | 8 | 29 | 0 | 9 | 1 | 11 |
| Oct 29 | vs. Arizona State | L 34–42 | 1 | 3 | 0 | 3 | – | – |
| Nov 5 | vs. Oregon | L 10–49 | – | – | – | – | – | – |
| Nov 19 | at Washington | L 7–54 | – | – | – | – | – | – |
| Nov 26 | vs.Utah | L 21–63 | 1 | −13 | 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.