Running back, Northern Colorado (from Drake), 2021–24
Caden Meis
- Number
- No. 27
- Height
- 5′11″
- Weight
- 216 lb
- Class (2024)
- Junior
- Hometown
- Parker, CO
Caden Meis played running back at Drake (2021) and Northern Colorado (2022–24).
Career highs
89rushing yards, career highvs. Portland State, 20232rushing touchdowns, career highvs. Abilene Christian, 2024Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2023 | Northern Colorado | 25 | 144 | 5.8 | 1 | 23 |
| 2024 | Northern Colorado | 96 | 337 | 3.5 | 4 | 24 |
| Career | 121 | 481 | 4.0 | 5 | 24 | |
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | Northern Colorado | 27 | RB | Fr. | ||
| 2023 | Northern Colorado | 27 | RB | So. | ||
| 2024 | Northern Colorado | 27 | RB | Jr. | 5′11″ | 216 |
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 |
|---|---|---|---|---|---|---|---|
| 2023 | Northern Colorado (FCS) | 26 | 0.24 | – | – | 6.2 | 10% |
| 2024 | Northern Colorado (FCS) | 102 | 0.13 | 40th (n=434) | 0.16 | 13.3 | 16% |
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 Northern Colorado 10 games, 337 rushing yards, 4 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 14 | vs. | L 22–24 | 19 | 44 | 2 | 7 | – | – |
| Sep 21 | at | L 7–48 | 9 | 24 | 0 | 24 | – | – |
| Sep 28 | vs. | L 7–28 | 4 | 16 | 0 | 6 | – | – |
| Oct 5 | at | L 17–55 | 10 | 35 | 0 | 10 | 1 | 16 |
| Oct 12 | at | W 21–17 | 14 | 60 | 1 | 10 | 1 | 1 |
| Oct 26 | vs. | L 0–24 | 4 | 1 | 0 | 3 | 2 | 17 |
| Nov 2 | at | L 7–59 | 11 | 44 | 1 | 14 | 2 | 14 |
| Nov 9 | vs. | L 15–43 | 5 | 14 | 0 | 8 | – | – |
| Nov 16 | vs. | L 3–44 | 10 | 67 | 0 | 17 | – | – |
| Nov 23 | at | L 13–45 | 10 | 32 | 0 | 8 | 1 | 1 |
2023 Northern Colorado 5 games, 144 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 9 | vs. | L 7–42 | 2 | 9 | 0 | 8 | – | – |
| Sep 16 | at | L 21–64 | 2 | 19 | 0 | 11 | 1 | 0 |
| Nov 4 | vs. | L 13–27 | 4 | 18 | 0 | 15 | – | – |
| Nov 11 | at | L 7–28 | 1 | 9 | 0 | 9 | – | – |
| Nov 18 | vs. | L 23–27 | 16 | 89 | 1 | 23 | 1 | 8 |
2022 Northern Colorado 2 games, 3 returns, 33 yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. | L 34–46 | – | – | – | – | – | – |
| Sep 10 | at | L 10–33 | – | – | – | – | – | – |
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.
