Defensive back, Campbell, 2020–22
Josh McNeely
- Number
- No. 30
- Height
- 5′8″
- Weight
- 160 lb
- Class (2022)
- Senior
- Hometown
- Charlotte, NC
Josh McNeely played defensive back at Campbell (2020–22).
Returns
Defense
Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.
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
2022 Campbell 11 games, 35 returns, 626 yards
| Date | Opponent | Result | KR | Yds | PR | Yds | TD |
|---|---|---|---|---|---|---|---|
| Sep 1 | vs. The Citadel | W 29–10 | 2 | 19 | – | – | 0 |
| Sep 10 | at William & Mary | L 21–37 | 4 | 104 | – | – | 0 |
| Sep 17 | at East Carolina | L 10–49 | 5 | 90 | 1 | 0 | 0 |
| Oct 1 | vs. North Carolina Central | W 48–18 | 1 | 7 | 1 | 5 | 0 |
| Oct 8 | vs. Charleston Southern | W 34–28 | 2 | 53 | 2 | 29 | 0 |
| Oct 15 | vs. Robert Morris | W 41–10 | 2 | 55 | – | – | 0 |
| Oct 22 | at Jackson State | L 14–22 | 2 | 59 | 1 | 6 | 0 |
| Oct 29 | at North Carolina A&T | L 38–45 | 1 | 17 | – | – | 0 |
| Nov 5 | at Bryant | L 37–43 | 4 | 69 | – | – | 0 |
| Nov 12 | vs. Gardner-Webb | L 35–42 | 5 | 95 | – | – | 0 |
| Nov 19 | at Delaware State | W 34–7 | 1 | 19 | 1 | −1 | 0 |
2021 Campbell 1 game, 1 return, 15 yards
| Date | Opponent | Result | KR | Yds | PR | Yds | TD |
|---|---|---|---|---|---|---|---|
| Sep 4 | at Liberty | L 7–48 | 1 | 15 | – | – | 0 |
2020 Campbell 2 games, 5 tackles
| Date | Opponent | Result | KR | Yds | PR | Yds | TD |
|---|---|---|---|---|---|---|---|
| Sep 18 | at Coastal Carolina | L 21–43 | – | – | – | – | – |
| Sep 26 | at App State | L 21–52 | – | – | – | – | – |
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.