Tight end, Air Force, 2009–11
Joshua Freeman
- Number
- No. 81
- Height
- 6′3″
- Hometown
- Anacortes, WA
Joshua Freeman played tight end at Air Force (2009–11).
Receiving
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.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2009 | 5 | 2 | 3 | 5 |
| 2010 | 6 | 4 | 1 | 5 |
| 2011 | 7 | 1 | 0 | 1 |
| On file | 7 | 4 | 11 | |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in). A dash: the source has no number for it.
On the roster
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 Air Force 6 games, 14 catches, 154 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 10 | vs. TCU | L 19–35 | 5 | 38 | 0 | 16 | −1 |
| Sep 24 | vs. Tennessee State | W 63–24 | 2 | 20 | 1 | 13 | – |
| Oct 8 | at Notre Dame | L 33–59 | 2 | 32 | 0 | 17 | – |
| Oct 22 | at Boise State | L 26–37 | 2 | 34 | 0 | 18 | – |
| Nov 5 | vs. Army | W 24–14 | 2 | 25 | 0 | 21 | – |
| Dec 28 ✦ | vs. Toledo | L 41–42 | 1 | 5 | 0 | 5 | – |
2010 Air Force 4 games, 4 catches, 122 yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Oct 9 | vs. Colorado State | W 49–27 | 1 | 51 | 0 | 51 | – |
| Oct 16 | at San Diego State | L 25–27 | 1 | 9 | 0 | 9 | – |
| Oct 23 | atTCU | L 7–38 | 1 | 17 | 0 | 17 | – |
| Oct 30 | vs. Utah | L 23–28 | 1 | 45 | 0 | 45 | – |
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.