Receiver, Sacred Heart, 2023–24
Ethan Hilliman
Ethan Hilliman played receiver at Sacred Heart (2023–24).
Career highs
9catches, career highvs. Delaware State, 2024Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2023 | Sacred Heart | 17 | 190 | 11.2 | 1 | 33 |
| 2024 | Sacred Heart | 32 | 315 | 9.8 | 3 | 44 |
| Career | 49 | 505 | 10.3 | 4 | 44 | |
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
2024 Sacred Heart 10 games, 32 catches, 315 yards, 3 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Aug 31 | vs. Delaware State | L 15–17 | 9 | 75 | 0 | 13 | – |
| Sep 7 | vs.Saint Anselm | W 10–3 | 2 | 16 | 0 | 16 | – |
| Sep 14 | vs. Georgetown | W 40–14 | 4 | 71 | 1 | 44 | – |
| Sep 21 | at Stonehill | L 21–35 | 3 | 24 | 1 | 17 | – |
| Sep 28 | at Delaware | L 0–49 | 4 | 15 | 0 | 16 | 1 |
| Oct 5 | vs. Norfolk State | W 10–3 | 3 | 11 | 0 | 5 | – |
| Oct 12 | at Howard | L 14–21 | 2 | 13 | 0 | 8 | – |
| Oct 19 | at Lafayette | L 17–31 | 1 | 24 | 0 | 24 | – |
| Oct 26 | vs. Mercyhurst | W 31–14 | 1 | 37 | 0 | 37 | – |
| Nov 9 | vs. Long Island University | L 7–28 | 3 | 29 | 1 | 20 | – |
2023 Sacred Heart 8 games, 17 catches, 190 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 2 | vs.Lafayette | L 14–19 | 4 | 28 | 1 | 11 | – |
| Sep 23 | atSaint Francis | W 37–34 | 2 | 37 | 0 | 28 | – |
| Sep 30 | vs. Merrimack | L 7–17 | 1 | 11 | 0 | 11 | – |
| Oct 7 | atLong Island University | L 13–23 | 4 | 53 | 0 | 33 | – |
| Oct 14 | at Yale | L 3–31 | 2 | 20 | 0 | 12 | – |
| Oct 21 | atStonehill | L 19–22 | 2 | 20 | 0 | 12 | – |
| Oct 28 | vs. Duquesne | L 0–27 | 1 | 9 | 0 | 9 | – |
| Nov 18 | at UConn | L 3–31 | 1 | 12 | 0 | 12 | – |
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.