Head to Head
| NCAA Division I, FCS, Playoffs | 2016/12/04 01:00 | 버지니아 테크 v Clemson | L | 35-42 |
| NCAA Division I, FCS, Playoffs | 2012/10/20 12:00 | Clemson v 버지니아 테크 | L | 38-17 |
| NCAA Division I, FCS, Playoffs | 2011/12/03 12:00 | Clemson v 버지니아 테크 | L | 38-10 |
| NCAA Division I, FCS, Playoffs | 2011/10/01 12:00 | 버지니아 테크 v Clemson | L | 3-23 |
| NCAA Division I, FCS, Playoffs | 2007/10/06 12:00 | Clemson v 버지니아 테크 | W | 23-41 |
| NCAA Division I, FCS, Playoffs | 2006/10/26 12:00 | 버지니아 테크 v Clemson | W | 24-7 |
| Collegiate Bowl Games | 2001/01/01 12:00 | Clemson v 버지니아 테크 | W | 20-41 |
Home History
| NCAA Division I, FCS, Playoffs | 2017/09/23 18:00 | Old Dominion v 버지니아 테크 | W | 0-38 |
| NCAA Division I, FCS, Playoffs | 2017/09/16 19:30 | 버지니아 테크 v 이스트 캐롤라이나 | W | 64-17 |
| NCAA Division I, FCS, Playoffs | 2017/09/09 19:30 | 댈라웨어 블루 헨즈 v 버지니아 테크 | W | 0-27 |
| NCAA Division I, FCS, Playoffs | 2017/09/03 23:30 | 웨스트 버지니아 마운티너즈 v 버지니아 테크 | W | 24-31 |
| NCAA Division I, FCS, Playoffs | 2016/12/29 22:30 | 아칸소 레이져백스 v 버지니아 테크 | W | 24-35 |
| NCAA Division I, FCS, Playoffs | 2016/12/04 01:00 | 버지니아 테크 v Clemson | L | 35-42 |
| NCAA Division I, FCS, Playoffs | 2016/11/26 17:00 | 버지니아 케벌리어즈 v 버지니아 테크 | W | 10-52 |
| NCAA Division I, FCS, Playoffs | 2016/11/19 20:30 | 버지니아 테크 v 노트르담 | W | 34-31 |
Away History
| NCAA Division I, FCS, Playoffs | 2017/09/23 19:30 | Clemson v 보스턴 칼리지 이글즈 | W | 34-7 |
| NCAA Division I, FCS, Playoffs | 2017/09/23 19:30 | 보스턴 칼리지 이글즈 v Clemson | W | 7-34 |
| NCAA Division I, FCS, Playoffs | 2017/09/17 00:00 | Clemson v Louisville | W | 47-21 |
| NCAA Division I, FCS, Playoffs | 2017/09/09 23:00 | 오번 v Clemson | W | 6-14 |
| NCAA Division I, FCS, Playoffs | 2017/09/02 16:00 | Kent State v Clemson | W | 3-56 |
| NCAA Division I, FCS, Playoffs | 2017/01/10 01:00 | Clemson v Alabama A&M | W | 35-31 |
| NCAA Division I, FCS, Playoffs | 2017/01/01 00:00 | Ohio State v Clemson | W | 0-31 |
| NCAA Division I, FCS, Playoffs | 2016/12/04 01:00 | 버지니아 테크 v Clemson | W | 35-42 |
We're selling API, please Contact Us