Quarterback, Concord (from Kent State), 2022–⁠26

Devin Kargman

Number
No. 15
Height
6′3″
Weight
225 lb
Class (2026)
Junior
Hometown
Camden, NJ

Devin Kargman plays quarterback for Concord, after Kent State (2022–⁠25). Last time out, at Davidson: 17 of 34, 225 yards, 1 TD.

2026 so far

225 passing yards, 1 TD

Last game: 17 of 34, 225 yards, 1 TD at Davidson, W 41–⁠35

Next game: at West Virginia Wesleyan, Oct 24

Career highs

255passing yards, career highvs. Northern Illinois, 2023

Passing

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

* The season in progress, so far.

SeasonTeamCmpAttPctYdsY/ATDInt
2022Kent State297041.43485.033
2023Kent State214151.23077.520
2024Kent State458254.94325.332
2025Kent State81747.1744.401
2026*Concord173450.02256.610
Career12024449.21,3865.796

Rushing

SeasonTeamCarYdsAvgTDLong
2022Kent State7−27−3.903
2023Kent State5−29−5.800
2024Kent State11−31−2.8012
2025Kent State3−20−6.700
Career26−107−4.1012

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

SeasonTeamNo.PosClassHtWt
2022Kent State15QBYr 1
2023Kent State15QBYr 2
2024Kent State15QBYr 3
2025Kent State15QBYr 4
2026Concord15QBJr. (Yr 5)6′3″225

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
2022Kent State540.20––10.621%
2023Kent State430.17––7.425%
2024Kent State890.13––11.241%
2025Kent State18-0.18––-3.2–

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 Concord 1 game, 225 passing yards, 1 TD
DateOpponentResultCmpAttYdsTDIntRush
Aug 27atDavidsonW 41–⁠35173422510–

No box score in the source for Sep 5 vs. Bluefield State; Sep 17 vs. Charleston (WV); Sep 26 at West Liberty; Oct 3 vs. Frostburg State; Oct 10 at West Virginia State; Oct 17 vs. Glenville State, so those games are not listed.

2025 Kent State 2 games, 74 passing yards
DateOpponentResultCmpAttYdsTDIntRush
Oct 4atOklahomaL 0–⁠448167401−20
Oct 18atToledoL 10–⁠4501000–
2024 Kent State 4 games, 432 passing yards, 3 TD
DateOpponentResultCmpAttYdsTDIntRush
Aug 31atPittsburghL 24–⁠55142818121−30
Sep 7vs.Saint FrancisL 17–⁠232238193111
Sep 14atTennesseeL 0–⁠719155800–
Sep 21atPenn StateL 0–⁠5601000−2
2023 Kent State 3 games, 307 passing yards, 2 TD
DateOpponentResultCmpAttYdsTDIntRush
Nov 1atAkronL 27–⁠31–––––−5
Nov 18atBall StateL 3–⁠345125200−16
Nov 25vs.Northern IllinoisL 27–⁠37162925520−8
2022 Kent State 6 games, 348 passing yards, 3 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 3atWashingtonL 20–⁠45251501–
Sep 10atOklahomaL 3–⁠3302001–
Sep 17vs.Long Island UniversityW 63–⁠1011410−4
Oct 22vs.AkronW 33–⁠271425213204
Nov 16vs.Eastern MichiganL 24–⁠317199100−19
Nov 26atBuffaloW 30–⁠275182501−8

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.