Quarterback, App State (from Memphis, Texas State), 2017–⁠22

Brady McBride

Number
No. 11
Height
6′0″
Weight
200 lb
Class (2022)
Junior
Hometown
Coppell, TX

Brady McBride played quarterback at Memphis (2017–⁠18), Texas State (2019–⁠21) and App State (2022).

At a glance

Best season
1,928
Passing yards, 2020 (Texas State, 2–⁠10)
Best game
443 yards
Vs. Arkansas State, week 12, 2020: No. 2 passing game in FBS that week

Career highs

443passing yards, career highvs. Arkansas State, 20205touchdown passes, career highvs. Arkansas State, 2020

Passing

Passing yards, season by season, with his team’s record
SeasonTeamCmpAttPctYdsY/ATDInt
2018Memphis81457.1886.301
2020Texas State17228261.01,9286.8177
2021Texas State14624459.81,5076.21210
2022App State2366.73311.000
Career32854360.43,5566.52918

Rushing

SeasonTeamCarYdsAvgTDLong
2018Memphis7314.4017
2020Texas State64761.2023
2021Texas State771411.8119
2022App State133.003
Career1492511.7123

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2017Memphis11QBYr 1
2018Memphis11QBYr 2
2019Texas State11QBYr 3
2020Texas State11QBYr 4
2021Texas State11QBYr 5
2022App State11QBJr. (Yr 6)6′0″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

SeasonTeamPlaysEPA/playPctileMedianTotalUsageAdj. passAdj. rush
2018Memphis21-0.18––-3.89%––
2020Texas State3430.1110th (n=116)0.2737.860%0.22-0.11
2021Texas State3030.2119th (n=145)0.3363.459%0.330.25
2022App State40.61––2.4–––

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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.

Game by game

2022 App State 1 game, 33 passing yards
DateOpponentResultCmpAttYdsTDIntRush
Oct 1vs.The CitadelW 49–⁠02333003
2021 Texas State 7 games, 1,507 passing yards, 12 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 4vs.BaylorL 20–⁠29204015613−7
Sep 11atFlorida InternationalW 23–⁠1718311651053
Sep 18vs.Incarnate WordL 34–⁠4225412782018
Sep 25atEastern MichiganL 21–⁠59162518730−28
Oct 9vs.South AlabamaW 33–⁠3118281872357
Oct 16vs.TroyL 28–⁠312232279332
Oct 23atGeorgia StateL 16–⁠2827472550146
2020 Texas State 9 games, 1,928 passing yards, 17 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 5vs.SMUL 24–⁠312139227213
Sep 26atBoston CollegeL 21–⁠24192922921−14
Oct 10atTroyL 17–⁠371528931022
Oct 17atSouth AlabamaL 20–⁠302840260102
Oct 24atBYUL 14–⁠52163015322–
Oct 31vs.LouisianaL 34–⁠4414321661322
Nov 14atGeorgia SouthernL 38–⁠40713155207
Nov 21vs.Arkansas StateW 47–⁠4532454435014
Nov 28vs.Coastal CarolinaL 14–⁠4920262021020
2018 Memphis 5 games, 88 passing yards
DateOpponentResultCmpAttYdsTDIntRush
Sep 1vs.MercerW 66–⁠14610700023
Sep 14vs.Georgia StateW 59–⁠2201001–
Sep 28atTulaneL 24–⁠40––––––
Nov 3atEast CarolinaW 59–⁠41––––––
Nov 10vs.TulsaW 47–⁠212318008

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.