Receiver, Kansas (from Ball State), 2022–⁠26

Cam Pickett

Lettered 2024 at Ball State (school media guide)

Number
No. 7
Height
6′0″
Weight
195 lb
Class (2026)
Senior
Hometown
Chicago, IL

Cam Pickett plays receiver for Kansas, after Ball State (2022–⁠24). Last time out, at Kansas State: 1 catch, 4 yards.

2026 so far

17 catches, 193 yards

Last game: 1 catch, 4 yards at Kansas State, L 24–⁠35

Next game: vs. Baylor, Oct 24

Game by game this season, receiving yards
  1. 6MIZ
  2. 49MTSU
  3. 134@UTAH
  4. 4@KSU

Filled bars: wins; outlined: losses.

Career highs

9catches, career highat Ohio, 2024134receiving yards, career highat Utah, 20262receiving touchdowns, career highvs. Fresno State, 2025

Receiving

Receiving yards, season by season, with his team’s record

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2024Ball State4952810.8265
2025Kansas4544910.0338
2026Kansas1719311.4032
Career1111,17010.5565

Returns

SeasonTeamKRYdsTD
2024Ball State51300
2025Kansas1380
Career61680

Rushing

SeasonTeamCarYdsAvgTDLong
2024Ball State1717010.0234
2025Kansas22010.0019
2026Kansas155.005
Career201959.8234

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Ball State7WRRS
2023Ball State7WRFr.
2024Ball State7WRSo.
2025Kansas7WRJr.
2026Kansas7WRSr.6′0″195

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

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2024Ball State770.6214th (n=581)0.9247.610%
2025Kansas630.5260th (n=1040)0.4632.58%
2026Kansas310.078th (n=829)0.432.011%

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

2026 Kansas 4 games, 17 catches, 193 yards
DateOpponentResultRecYdsTDLongRush
Sep 11vs.MissouriL 21–⁠382603–
Oct 3vs.Middle TennesseeW 55–⁠0649022–
Oct 10atUtahL 24–⁠4181340325
Oct 17atKansas StateL 24–⁠351404–
2025 Kansas 12 games, 45 catches, 449 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Aug 23vs.Fresno StateW 31–⁠7677221–
Aug 29vs.WagnerW 46–⁠7229120–
Sep 6atMissouriL 31–⁠42218012–
Sep 20vs.West VirginiaW 41–⁠101808–
Sep 27vs.CincinnatiL 34–⁠37231027–
Oct 4atUCFW 27–⁠205640381
Oct 11atTexas TechL 17–⁠42655019–
Oct 25vs.Kansas StateL 17–⁠42640014–
Nov 1vs.Oklahoma StateW 38–⁠213120919
Nov 8atArizonaL 20–⁠24362026–
Nov 22atIowa StateL 14–⁠38422011–
Nov 28vs.UtahL 21–⁠31531025–
2024 Ball State 12 games, 49 catches, 528 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Sep 7vs.Missouri StateW 42–⁠3476902110
Sep 14atMiamiL 0–⁠622807–
Sep 21atCentral MichiganL 34–⁠37528013–
Sep 28atJames MadisonL 7–⁠638530146
Oct 5vs.Western MichiganL 42–⁠451271274
Oct 12atKent StateW 37–⁠3544601930
Oct 19atVanderbiltL 14–⁠24240029–
Oct 26vs.Northern IllinoisW 25–⁠23––––44
Nov 5vs.Miami (OH)L 21–⁠274180815
Nov 12atBuffaloL 48–⁠5137416537
Nov 23vs.Bowling GreenL 13–⁠38446017−3
Nov 29atOhioL 21–⁠42911903127

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.