Receiver, Akron, 2009–⁠10

Jeremy LaFrance

Number
No. 82
Height
6′1″
Hometown
Belle Chasse, LA

Jeremy LaFrance played receiver at Akron (2009–⁠10).

Career highs

8catches, career highvs. Kent State, 2009126receiving yards, career highvs. Kent State, 20092receiving touchdowns, career highthree times; last at Ball State, 2010

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2009Akron4352012.1259
2010Akron4353412.4637
Career861,05412.3859

Returns

SeasonTeamKRYdsTDPRYdsTD
2009Akron386015220
2010Akron5102013220
Career8188028440

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2009Akron82WR
2010Akron82WR6′1″

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

2010 Akron 9 games, 43 catches, 534 yards, 6 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 4vs.SyracuseL 3–⁠2977505102–
Sep 11vs.Gardner-WebbL 37–⁠387881––2
Sep 18atKentuckyL 10–⁠471230––1
Sep 25atIndianaL 20–⁠352462––2
Oct 2vs.Northern IllinoisL 14–⁠505570––1
Oct 9atKent StateL 17–⁠286750––4
Nov 6atBall StateL 30–⁠373462–––
Nov 17vs.Miami (OH)L 14–⁠196590––2
Nov 26vs.BuffaloW 22–⁠146651––1
2009 Akron 12 games, 43 catches, 520 yards, 2 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 5atPenn StateL 7–⁠315530–––
Sep 12vs.Morgan StateW 41–⁠0–––––1
Sep 19vs.IndianaL 21–⁠383100–––
Sep 26atCentral MichiganL 21–⁠483540–––
Oct 10vs.OhioL 7–⁠195650–––
Oct 17atBuffaloL 17–⁠215620–––
Oct 24atSyracuseL 14–⁠285460–––
Oct 31atNorthern IllinoisL 10–⁠271180–––
Nov 7vs.Kent StateW 28–⁠2081262––4
Nov 13vs.TempleL 17–⁠5621501382
Nov 20atBowling GreenL 20–⁠3621201313
Nov 27vs.Eastern MichiganW 28–⁠2145901175

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.