Receiver, Colorado State (from Northern Arizona), 2024–25
Tay Lanier
- Number
- No. 6
- Height
- 6′1″
- Weight
- 165 lb
- Class (2025)
- Senior
- Hometown
- Long Beach, CA
Tay Lanier played receiver at Northern Arizona (2024) and Colorado State (2025).
Career highs
9catches, career highvs. Air Force, 2025122receiving yards, career highvs. Eastern Washington, 2024Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2024 | Northern Arizona | 27 | 457 | 16.9 | 4 | 52 |
| 2025 | Colorado State | 35 | 315 | 9.0 | 2 | 39 |
| Career | 62 | 772 | 12.5 | 6 | 52 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2024 | Northern Arizona | 6 | WR | Jr. | ||
| 2025 | Colorado State | 6 | WR | Sr. | 6′1″ | 165 |
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 |
|---|---|---|---|---|---|---|---|
| 2024 | Northern Arizona (FCS) | 20 | 1.25 | – | – | 25.0 | 4% |
| 2025 | Colorado State | 47 | 0.46 | 51st (n=1040) | 0.46 | 21.7 | 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
2025 Colorado State 12 games, 35 catches, 315 yards, 2 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 30 | at Washington | L 21–38 | 1 | 10 | 0 | 10 |
| Sep 6 | vs. Northern Colorado | W 21–17 | – | – | – | – |
| Sep 20 | vs. UTSA | L 16–17 | 3 | 17 | 0 | 6 |
| Sep 27 | vs. Washington State | L 3–20 | 2 | 12 | 0 | 9 |
| Oct 3 | at San Diego State | L 24–45 | 1 | 14 | 0 | 14 |
| Oct 10 | vs. Fresno State | W 49–21 | 1 | 4 | 0 | 4 |
| Oct 18 | vs. Hawai’i | L 19–31 | 2 | 56 | 0 | 37 |
| Oct 25 | at Wyoming | L 0–28 | 3 | 56 | 0 | 39 |
| Nov 8 | vs. UNLV | L 10–42 | 3 | 6 | 0 | 6 |
| Nov 15 | at New Mexico | L 17–20 | 5 | 41 | 0 | 15 |
| Nov 22 | at Boise State | L 21–49 | 5 | 26 | 1 | 8 |
| Nov 28 | vs. Air Force | L 21–42 | 9 | 73 | 1 | 20 |
2024 Northern Arizona 12 games, 27 catches, 457 yards, 4 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 31 | vs.Lincoln (CA) | W 66–6 | 1 | 17 | 0 | 17 |
| Sep 7 | at Arizona | L 10–22 | 1 | 21 | 0 | 21 |
| Sep 14 | at Utah Tech | W 45–17 | 1 | 15 | 0 | 15 |
| Sep 21 | at Incarnate Word | L 14–38 | 2 | 40 | 1 | 37 |
| Sep 28 | vs. Sacramento State | W 34–16 | 7 | 69 | 1 | 16 |
| Oct 5 | at Idaho | L 17–23 | 4 | 50 | 0 | 16 |
| Oct 12 | at Montana | L 20–31 | 1 | 6 | 0 | 6 |
| Oct 19 | vs. Idaho State | W 30–26 | 2 | 44 | 0 | 39 |
| Nov 2 | vs. Weber State | W 27–6 | 1 | 15 | 0 | 15 |
| Nov 9 | at Cal Poly | W 31–14 | 1 | 22 | 1 | 22 |
| Nov 23 | vs. Eastern Washington | W 30–18 | 5 | 122 | 1 | 52 |
| Nov 30 | at Abilene Christian | L 0–24 | 1 | 36 | 0 | 36 |
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.