Running back, William & Mary, 2013–16
Kendell Anderson
Kendell Anderson played running back at William & Mary (2013–16).
Team titles: Coastal Athletic Association Football champions, 2015
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2013 | William & Mary | 11 | 31 | 2.8 | 0 | 12 |
| 2014 | William & Mary | 3 | 20 | 6.7 | 0 | 9 |
| 2015 | William & Mary | 8 | 51 | 6.4 | 0 | 16 |
| 2016 | William & Mary | 5 | 8 | 1.6 | 0 | 5 |
| Career | 27 | 110 | 4.1 | 0 | 16 | |
Season lines from CollegeFootballData, regular season and bowls.
Per play
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2013 | William & Mary (FCS) | 13 | -0.06 | – | – | -0.8 | – |
| 2014 | William & Mary (FCS) | 5 | 0.30 | – | – | 1.5 | – |
| 2015 | William & Mary (FCS) | 8 | 0.34 | – | – | 2.7 | – |
| 2016 | William & Mary (FCS) | 7 | -0.66 | – | – | -4.6 | – |
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
2016 William & Mary 1 game, 8 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 1 | at NC State | L 14–48 | 5 | 8 | 0 | 5 | 1 | −2 |
No box score in the source for Sep 10 at Hampton; Sep 17 vs. Norfolk State; Sep 24 vs. Elon; Oct 1 at New Hampshire; Oct 8 at James Madison; Oct 15 vs. Delaware; Oct 29 vs. Maine; Nov 5 at Stony Brook; Nov 12 at Towson; Nov 19 vs. Richmond, so those games are not listed.
2015 William & Mary 1 game, 51 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 19 | at Virginia | L 29–35 | 8 | 51 | 0 | 16 | – | – |
No box score in the source for Sep 5 at Lafayette; Sep 26 vs. Stony Brook; Oct 3 at Delaware; Oct 10 at Villanova; Oct 17 vs. New Hampshire; Oct 24 vs. Hampton; Oct 31 vs. James Madison; Nov 7 at Elon; Nov 14 vs. Towson; Nov 21 at Richmond; Nov 28 vs. Duquesne; Dec 5 at Richmond, so those games are not listed.
2014 William & Mary 1 game, 20 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | at Virginia Tech | L 9–34 | 3 | 20 | 0 | 9 | 1 | 11 |
No box score in the source for Sep 6 at Hampton; Sep 13 vs. Norfolk State; Sep 20 vs. Lafayette; Sep 27 at Stony Brook; Oct 11 at New Hampshire; Oct 18 vs. Villanova; Oct 25 vs. Delaware; Nov 1 at James Madison; Nov 8 vs. Elon; Nov 15 at Towson; Nov 23 vs. Richmond, so those games are not listed.
2013 William & Mary 1 game, 31 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 31 | at West Virginia | L 17–24 | 11 | 31 | 0 | 12 | 2 | 13 |
No box score in the source for Sep 7 vs. Hampton; Sep 14 at Lafayette; Sep 21 vs. Rhode Island; Oct 5 at Villanova; Oct 12 vs. Pennsylvania; Oct 19 at Maine; Oct 26 vs. James Madison; Nov 2 vs. New Hampshire; Nov 9 at Delaware; Nov 16 vs. Towson; Nov 23 at Richmond, so those games are not listed.
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.