Receiver, Utah Tech (from Liberty), 2020–23
Jaivian Lofton
- Number
- No. 6
- Height
- 6′1″
- Weight
- 200 lb
- Class (2023)
- Junior
- Hometown
- Rancho Cucamonga, CA
Jaivian Lofton played receiver at Liberty (2020–22) and Utah Tech (2023).
Career highs
105receiving yards, career highat North Alabama, 2023Receiving
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 |
|---|---|---|---|---|---|---|
| 2020 | Liberty | 6 | WR | Yr 1 | ||
| 2021 | Liberty | 6 | WR | Yr 2 | ||
| 2022 | Liberty | 6 | WR | Yr 3 | ||
| 2023 | Utah Tech | 6 | WR | Jr. (Yr 4) | 6′1″ | 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 |
|---|---|---|---|---|---|---|---|
| 2020 | Liberty | 4 | 1.54 | – | – | 6.2 | – |
| 2021 | Liberty | 3 | 1.71 | – | – | 5.1 | – |
| 2022 | Liberty | 10 | 1.18 | – | – | 11.8 | – |
| 2023 | Utah Tech (FCS) | 39 | 0.41 | 10th (n=681) | 0.80 | 16.0 | 6% |
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 Utah Tech 10 games, 25 catches, 472 yards, 3 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 1 | at Montana State | L 20–63 | 2 | 68 | 0 | 62 |
| Sep 9 | vs. Montana | L 13–43 | 4 | 95 | 1 | 50 |
| Sep 16 | at Northern Arizona | W 50–36 | 1 | 17 | 1 | 17 |
| Sep 23 | at Missouri State | L 14–59 | 4 | 32 | 0 | 20 |
| Sep 30 | at Colorado State | L 20–41 | 1 | 15 | 0 | 15 |
| Oct 7 | vs. Stephen F. Austin | W 37–31 | 2 | 15 | 0 | 10 |
| Oct 21 | at North Alabama | L 30–31 | 4 | 105 | 0 | 42 |
| Oct 28 | vs. Eastern Kentucky | L 30–34 | 3 | 34 | 0 | 25 |
| Nov 11 | at Austin Peay | L 17–30 | 2 | 72 | 1 | 68 |
| Nov 18 | vs. Southern Utah | L 16–24 | 2 | 19 | 0 | 16 |
2022 Liberty 5 games, 10 catches, 102 yards, 2 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 3 | at Southern Miss | W 29–27 | 1 | −1 | 0 | 0 |
| Sep 24 | vs. Akron | W 21–12 | 4 | 47 | 0 | 13 |
| Oct 1 | at Old Dominion | W 38–24 | 2 | 44 | 1 | 34 |
| Oct 15 | vs. Gardner-Webb | W 21–20 | 2 | 6 | 0 | 4 |
| Nov 26 | vs. New Mexico State | L 14–49 | 1 | 6 | 1 | 6 |
2021 Liberty 1 game, 3 catches, 51 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 4 | vs. Campbell | W 48–7 | 3 | 51 | 1 | 27 |
2020 Liberty 3 games, 3 catches, 51 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 19 | at Western Kentucky | W 30–24 | 1 | 8 | 0 | 8 |
| Oct 3 | vs.North Alabama | W 28–7 | 1 | 9 | 0 | 9 |
| Oct 10 | vs. UL Monroe | W 40–7 | 1 | 34 | 0 | 34 |
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.