2015 Furman Paladins football team

The 2015 Furman Paladins football team represented Furman University in the 2015 NCAA Division I FCS football season. They were led by fifth year head coach Bruce Fowler and played their home games at Paladin Stadium. They were a member of the Southern Conference. They finished the season 4–7, 2–5 in SoCon play to finish in a tie for sixth place.

2015 Furman Paladins football
ConferenceSouthern Conference
2015 record4–7 (2–5 SoCon)
Head coachBruce Fowler (5th season)
Offensive coordinatorTim Sorrells
Defensive coordinatorKyle Gillenwater
Home stadiumPaladin Stadium
(Capacity: 16,000)
2015 Southern Conference football standings
Conf  Overall
Team W L    W L 
No. 9 Chattanooga +^  6 1     9 4  
No. 13 The Citadel +^  6 1     9 4  
Western Carolina  5 2     7 4  
Samford  3 4     6 5  
Wofford  3 4     5 6  
Mercer  2 5     5 6  
Furman  2 5     4 7  
VMI  1 6     2 9  
  • + Conference co-champions
  • ^ FCS playoff participant
Rankings from STATS FCS Poll

Schedule

DateTimeOpponentSiteTVResultAttendance
September 57:00 PMNo. 5 Coastal Carolina*ESPN3L 35–386,563
September 123:30 PMat Virginia Tech*ESPN3L 3–4260,118
September 196:00 PMat UCF*
ESPN3W 16–1536,484
September 263:00 PMVMI
  • Paladin Stadium
  • Greenville, SC
ESPN3W 24–217,915
October 37:00 PMSouth Carolina State*
  • Paladin Stadium
  • Greenville, SC
ESPN3W 17–31,022
October 101:00 PMat No. 6 ChattanoogaESPN3L 3–317,630
October 241:30 PMThe Citadel
  • Paladin Stadium
  • Greenville, SC (Rivalry)
ESPN3L 17–3812,124
October 313:00 PMat SamfordSDNW 20–174,013
November 73:30 PMat Western CarolinaSDNL 10–488,561
November 141:30 PMMercer
  • Paladin Stadium
  • Greenville, SC
ESPN3L 20–27 OT6,351
November 213:30 PMat WoffordASNL 28–387,143
gollark: the trait bound `impl core::future::future::Future: warp::reply::Reply` is not satisfiedthe trait `warp::reply::Reply` is not implemented for `impl core::future::future::Future`note: required because of the requirements on the impl of `warp::reply::Reply` for `(impl core::future::future::Future,)`note: required because of the requirements on the impl of `warp::reply::Reply` for `warp::generic::Either<(impl core::future::future::Future,), (impl warp::reply::Reply,)>`note: required because of the requirements on the impl of `warp::reply::Reply` for `(warp::generic::Either<(impl core::future::future::Future,), (impl warp::reply::Reply,)>,)`note: required because of the requirements on the impl of `warp::reply::Reply` for `warp::generic::Either<(warp::filters::fs::File,), (warp::generic::Either<(impl core::future::future::Future,), (impl warp::reply::Reply,)>,)>`note: required because of the requirements on the impl of `warp::reply::Reply` for `(warp::generic::Either<(warp::filters::fs::File,), (warp::generic::Either<(impl core::future::future::Future,), (impl warp::reply::Reply,)>,)>,)`
gollark: If I change one line in my Rust code I can make it generate extremely incomprehensible type errors fairly easily.
gollark: Generally it would just randomly not compile with some incomprehensible type error.
gollark: That is quite something. Rust wouldn't have this issue, of course.
gollark: It's not unnecessary, just mostly unnecessary.

References


    This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.