Receiver, Purdue, 2003–05
Kyle Ingraham
- Hometown
- San Antonio, TX
Kyle Ingraham played receiver at Purdue (2003–05).
At a glance
Career highs
11catches, career highvs. Indiana, 2004209receiving yards, career highvs. Indiana, 20042receiving touchdowns, career hightwice; last vs. Indiana, 2004Receiving
Season lines from CollegeFootballData, regular season and bowls. Every season here is summed from the game box scores (the source has no season lines for them; a game missing from the box scores is missing here).
Game by game
2005 Purdue 10 games, 41 catches, 500 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 10 | vs. Akron | W 49–24 | 6 | 78 | 0 | 37 |
| Sep 17 | at Arizona | W 31–24 | 1 | 46 | 0 | 46 |
| Sep 24 | at Minnesota | L 35–42 | 1 | 9 | 0 | 9 |
| Oct 1 | vs. Notre Dame | L 28–49 | 7 | 91 | 0 | 22 |
| Oct 8 | vs. Iowa | L 17–34 | 10 | 117 | 0 | 17 |
| Oct 15 | vs. Northwestern | L 29–34 | 4 | 38 | 0 | 18 |
| Oct 22 | at Wisconsin | L 20–31 | 2 | 12 | 0 | 7 |
| Oct 29 | at Penn State | L 15–33 | 7 | 77 | 0 | 22 |
| Nov 5 | vs. Michigan State | W 28–21 | 1 | 5 | 0 | 5 |
| Nov 12 | vs. Illinois | W 37–3 | 2 | 27 | 0 | 16 |
2004 Purdue 11 games, 51 catches, 624 yards, 7 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 5 | vs. Syracuse | W 51–0 | 2 | 15 | 0 | 10 |
| Sep 11 | vs. Ball State | W 59–7 | 3 | 34 | 1 | 15 |
| Sep 25 | atIllinois | W 38–30 | 3 | 45 | 0 | 31 |
| Oct 2 | atNotre Dame | W 41–16 | 4 | 29 | 1 | 9 |
| Oct 9 | atPenn State | W 20–13 | 5 | 43 | 0 | 11 |
| Oct 16 | vs.Wisconsin | L 17–20 | 5 | 61 | 0 | 16 |
| Oct 30 | atNorthwestern | L 10–13 | 3 | 43 | 0 | 32 |
| Nov 6 | atIowa | L 21–23 | 6 | 70 | 1 | 22 |
| Nov 13 | vs. Ohio State | W 24–17 | 8 | 72 | 2 | 22 |
| Nov 20 | vs. Indiana | W 63–24 | 11 | 209 | 2 | 52 |
| Dec 31 ✦ | vs. Arizona State | L 23–27 | 1 | 3 | 0 | 3 |
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.