Receiver, Temple, 2011–⁠15

John Christopher

Number
No. 7
Height
5′11″
Hometown
Ormond Beach, FL

John Christopher played receiver at Temple (2011–⁠15).

Career highs

7catches, career hightwice; last at Massachusetts, 2015

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2012Temple912213.6133
2013Temple3133110.7239
2014Temple241948.1025
2015Temple2020810.4028
Career8485510.2339

Returns

SeasonTeamPRYdsTD
2014Temple8240

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTklTFL
201284150
2013N1273100.5
On file114150.5

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2011Temple7WR
2012Temple7WR
2013Temple7WR
2014Temple7WR
2015Temple7WR5′11″

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
2013Temple330.6631st (n=341)0.8121.65%
2014Temple390.022nd (n=496)0.520.98%
2015Temple290.62––17.95%

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

2015 Temple 9 games, 20 catches, 208 yards
DateOpponentResultRecYdsTDLongRush
Sep 5vs.Penn StateW 27–⁠10113013–
Sep 19atMassachusettsW 25–⁠23772019–
Oct 17vs.UCFW 30–⁠16128028–
Oct 22atEast CarolinaW 24–⁠141909–
Oct 31vs.Notre DameL 20–⁠24222012–
Nov 6atSMUW 60–⁠40328023–
Nov 14atSouth FloridaL 23–⁠44327012–
Nov 21vs.MemphisW 31–⁠121606–
Dec 22 ✦vs.ToledoL 17–⁠321303–
2014 Temple 9 games, 24 catches, 194 yards
DateOpponentResultRecYdsTDLongRush
Sep 6vs.NavyL 24–⁠3153209–
Sep 27atUConnW 36–⁠10430013–
Oct 11vs.TulsaW 35–⁠241404–
Oct 17atHoustonL 10–⁠31230025–
Oct 25atUCFL 14–⁠3452109–
Nov 1vs.East CarolinaW 20–⁠10–––––
Nov 7vs.MemphisL 13–⁠16323011–
Nov 15atPenn StateL 13–⁠30225016–
Dec 6atTulaneW 10–⁠3229016–
2013 Temple 10 games, 31 catches, 331 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Aug 31atNotre DameL 6–⁠28325011–
Sep 7vs.HoustonL 13–⁠221404−7
Sep 14vs.FordhamL 29–⁠30337016–
Sep 28atIdahoL 24–⁠26324015–
Oct 19vs.ArmyW 33–⁠14139139–
Oct 26atSMUL 49–⁠59226118–
Nov 2atRutgersL 20–⁠23541011–
Nov 16vs.UCFL 36–⁠39329017–
Nov 23vs.UConnL 21–⁠28766024–
Nov 30atMemphisW 41–⁠21340022−9
2012 Temple 6 games, 9 catches, 122 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 8vs.MarylandL 27–⁠361606–
Oct 6vs.South FloridaW 37–⁠28110010–
Oct 13atUConnW 17–⁠14112012–
Oct 27atPittsburghL 17–⁠47217012–
Nov 10vs.CincinnatiL 10–⁠34133033–
Nov 23vs.SyracuseL 20–⁠38344123–

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.