Rhode Island, 2006–07
Johnathan Pitt-Coombs
Johnathan Pitt-Coombs played at Rhode Island (2006–07).
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2006‡ | Rhode Island | 1 | 2 | 2.0 | 0 | 3 |
| 2007‡ | Rhode Island | 1 | 6 | 6.0 | 0 | 0 |
| Career | 2 | 8 | 4.0 | 0 | 3 | |
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). ‡ Short by 10 games in 2006 (Sep 9 vs. Merrimack; Sep 23 vs. Delaware; Sep 30 vs. Brown; Oct 7 at James Madison; Oct 14 vs. Richmond; Oct 21 at Massachusetts; Oct 28 vs. Maine; Nov 4 at Hofstra; Nov 11 vs. New Hampshire; Nov 18 at Northeastern) and 10 games in 2007 (Sep 1 vs. Fordham; Sep 15 at Delaware; Sep 22 vs. Hofstra; Sep 29 at Brown; Oct 13 vs. James Madison; Oct 20 at Richmond; Oct 27 at New Hampshire; Nov 3 vs. Massachusetts; Nov 10 at Maine; Nov 17 vs. Northeastern): the source has no box score for them.
Game by game
2007 Rhode Island 1 game, 6 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 8 | at Army | L 7–14 | 1 | 6 | 0 | 0 |
No box score in the source for Sep 1 vs. Fordham; Sep 15 at Delaware; Sep 22 vs. Hofstra; Sep 29 at Brown; Oct 13 vs. James Madison; Oct 20 at Richmond; Oct 27 at New Hampshire; Nov 3 vs. Massachusetts; Nov 10 at Maine; Nov 17 vs. Northeastern, so those games are not listed.
2006 Rhode Island 1 game, 2 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 31 | at UConn | L 7–52 | 1 | 2 | 0 | 3 |
No box score in the source for Sep 9 vs. Merrimack; Sep 23 vs. Delaware; Sep 30 vs. Brown; Oct 7 at James Madison; Oct 14 vs. Richmond; Oct 21 at Massachusetts; Oct 28 vs. Maine; Nov 4 at Hofstra; Nov 11 vs. New Hampshire; Nov 18 at Northeastern, so those games are not listed.
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.