Tight end, Wake Forest, 2007–⁠11

Cameron Ford

Number
No. 83
Height
6′4″
Hometown
Williamston, SC

Cameron Ford played tight end at Wake Forest (2007–⁠11).

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2008*Wake Forest188.008
2009Wake Forest1012012.0036
2010Wake Forest1112010.9034
2011Wake Forest12998.3321
On file (2008–⁠11)3434710.2336

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.PosHt
2008Wake Forest83TE
2009Wake Forest83TE
2010Wake Forest83TE
2011Wake Forest83TE6′4″

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.

Game by game

2011 Wake Forest 7 games, 12 catches, 99 yards, 3 TD
DateOpponentResultRecYdsTDLong
Sep 1atSyracuseL 29–⁠3631709
Oct 15vs.Virginia TechL 17–⁠381414
Oct 22atDukeW 24–⁠2321308
Oct 29atNorth CarolinaL 24–⁠491505
Nov 5vs.Notre DameL 17–⁠24116016
Nov 12atClemsonL 28–⁠31221118
Nov 19vs.MarylandW 31–⁠10223121
2010 Wake Forest 8 games, 11 catches, 120 yards
DateOpponentResultRecYdsTDLong
Sep 2vs.PresbyterianW 53–⁠131404
Sep 18atStanfordL 24–⁠681808
Sep 25atFlorida StateL 0–⁠311707
Oct 2vs.Georgia TechL 20–⁠24121021
Oct 9vs.NavyL 27–⁠28224019
Oct 30atMarylandL 14–⁠62215017
Nov 20vs.ClemsonL 10–⁠30236034
Nov 27atVanderbiltW 34–⁠131505
2009 Wake Forest 6 games, 10 catches, 120 yards
DateOpponentResultRecYdsTDLong
Sep 5vs.BaylorL 21–⁠241404
Sep 19vs.ElonW 35–⁠7257036
Sep 26atBoston CollegeL 24–⁠271303
Oct 17atClemsonL 3–⁠381909
Oct 24atNavyL 10–⁠13229018
Oct 31vs.MiamiL 27–⁠2831809
2008 Wake Forest 1 game, 1 catch, 8 yards
DateOpponentResultRecYdsTDLong
Nov 15atNC StateL 17–⁠211808

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.