Receiver, Temple, 2016–19
Travon Williams
- Number
- No. 26
- Height
- 5′8″
- Weight
- 170 lb
- Class (2019)
- Senior
- Hometown
- Philadelphia, PA
Travon Williams played receiver at Temple (2016–19).
Career highs
89receiving yards, career highvs. Bucknell, 2019Team titles: American champions, 2016
Receiving
Returns
Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2016 | Temple | 26 | WR | Fr. | ||
| 2017 | Temple | 26 | WR | So. | ||
| 2018 | Temple | 26 | WR | Jr. | ||
| 2019 | Temple | 26 | WR | Sr. | 5′8″ | 170 |
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 |
|---|---|---|---|---|---|---|---|
| 2016 | Temple | 2 | -0.55 | – | – | -1.1 | – |
| 2017 | Temple | 6 | -0.12 | – | – | -0.7 | – |
| 2018 | Temple | 7 | 1.17 | – | – | 8.2 | – |
| 2019 | Temple | 7 | 1.59 | – | – | 11.1 | – |
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
2019 Temple 5 games, 5 returns, 58 yards
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds | PR |
|---|---|---|---|---|---|---|---|---|
| Aug 31 | vs. Bucknell | W 56–12 | 1 | 89 | 1 | – | – | – |
| Sep 14 | vs. Maryland | W 20–17 | 1 | 18 | 0 | – | – | – |
| Oct 12 | vs. Memphis | W 30–28 | – | – | – | 1 | 16 | – |
| Oct 19 | at SMU | L 21–45 | 3 | 14 | 0 | 4 | 42 | – |
| Dec 27 ✦ | vs. North Carolina | L 13–55 | 1 | 4 | 0 | – | – | – |
2018 Temple 4 games, 5 catches, 77 yards
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds | PR |
|---|---|---|---|---|---|---|---|---|
| Oct 6 | vs. East Carolina | W 49–6 | 1 | 16 | 0 | – | – | – |
| Nov 17 | vs. South Florida | W 27–17 | 2 | 19 | 0 | – | – | – |
| Nov 24 | at UConn | W 57–7 | 1 | 29 | 0 | – | – | 1 |
| Dec 27 ✦ | vs. Duke | L 27–56 | 1 | 13 | 0 | 2 | 26 | – |
2017 Temple 5 games, 2 returns, 30 yards
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds | PR |
|---|---|---|---|---|---|---|---|---|
| Sep 30 | vs. Houston | L 13–20 | – | – | – | – | – | – |
| Oct 7 | atEast Carolina | W 34–10 | – | – | – | – | – | – |
| Oct 14 | vs.UConn | L 24–28 | – | – | – | – | – | – |
| Nov 10 | at Cincinnati | W 35–24 | – | – | – | – | – | – |
| Nov 18 | vs. UCF | L 19–45 | – | – | – | 2 | 30 | – |
2016 Temple 3 games, 3 returns, 63 yards
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds | PR |
|---|---|---|---|---|---|---|---|---|
| Sep 10 | vs. Stony Brook | W 38–0 | – | – | – | 1 | 26 | – |
| Sep 24 | vs. Charlotte | W 48–20 | – | – | – | 2 | 37 | – |
| Nov 19 | at Tulane | W 31–0 | – | – | – | – | – | – |
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.