Receiver, Houston Christian, 2022–23
Karl Reynolds
- Number
- No. 5
- Height
- 6′2″
- Weight
- 175 lb
- Class (2023)
- Junior
- Hometown
- Humble, TX
Karl Reynolds played receiver at Houston Christian (2022–23).
Career highs
9catches, career hightwice; last vs. East Texas A&M, 2023146receiving yards, career highvs. Lindenwood, 20223receiving touchdowns, career highat Lamar, 2022Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2022 | Houston Christian | 29 | 421 | 14.5 | 5 | 66 |
| 2023* | Houston Christian | 47 | 661 | 14.1 | 6 | 52 |
| Career | 76 | 1,082 | 14.2 | 11 | 66 | |
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 | Houston Christian | 5 | WR | So. | ||
| 2023 | Houston Christian | 5 | WR | Jr. | 6′2″ | 175 |
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 | Houston Christian (FCS) | 32 | 0.59 | 34th (n=683) | 0.71 | 18.8 | 8% |
| 2023 | Houston Christian (FCS) | 56 | 0.74 | 42nd (n=681) | 0.80 | 41.7 | 9% |
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
2023 Houston Christian 10 games, 47 catches, 661 yards, 6 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 2 | vs.Arkansas Baptist | W 66–0 | 2 | 55 | 1 | 34 | – |
| Sep 9 | at Western Kentucky | L 22–52 | 7 | 106 | 2 | 32 | −6 |
| Sep 16 | at UT Martin | L 7–66 | 1 | 20 | 0 | 20 | – |
| Sep 23 | at SE Louisiana | W 34–19 | 4 | 44 | 1 | 25 | – |
| Sep 30 | vs. Lamar | L 19–21 | 6 | 112 | 0 | 52 | – |
| Oct 7 | at Nicholls | L 7–38 | 3 | 21 | 0 | 9 | – |
| Oct 14 | vs. Prairie View A&M | W 30–0 | 5 | 27 | 0 | 12 | – |
| Oct 28 | vs. East Texas A&M | W 17–13 | 9 | 119 | 1 | 28 | – |
| Nov 11 | at McNeese | W 35–24 | 4 | 99 | 1 | 49 | – |
| Nov 18 | vs. Incarnate Word | L 24–45 | 6 | 58 | 0 | 36 | – |
No box score in the source for Nov 4 at Northwestern State, so that game is not listed.
2022 Houston Christian 7 games, 29 catches, 421 yards, 5 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 3 | at Northern Colorado | W 46–34 | 4 | 94 | 1 | 66 | – |
| Sep 10 | vs. Lindenwood | L 20–21 | 7 | 146 | 0 | 59 | – |
| Sep 24 | at Texas State | L 0–34 | 4 | 18 | 0 | 9 | – |
| Oct 1 | atLamar | W 37–34 | 9 | 109 | 3 | 40 | – |
| Oct 8 | vs.Nicholls | L 17–19 | 2 | 45 | 1 | 40 | −4 |
| Oct 15 | vs. Northwestern State | L 10–37 | 2 | 12 | 0 | 6 | – |
| Oct 22 | atEast Texas A&M | L 3–31 | 1 | −3 | 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.