Quarterback, Northern Colorado, 2013

Tim Tancik

Tim Tancik played quarterback at Northern Colorado (2013).

Career highs

161passing yards, career highat Wyoming, 2013

Passing

SeasonTeamCmpAttPctYdsY/ATDInt
2013Northern Colorado162955.21615.611

Rushing

SeasonTeamCarYdsAvgTDLong
2013Northern Colorado320.702

Season lines from CollegeFootballData, regular season and bowls.

Per play

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2013Northern Colorado (FCS)31-0.16––-4.940%

Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.

Game by game

2013 Northern Colorado 1 game, 161 passing yards, 1 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 14atWyomingL 7–⁠351629161112

No box score in the source for Aug 31 vs. Langston; Sep 7 vs. CSU Pueblo; Sep 21 vs. Northern Iowa; Sep 28 vs. Southern Utah; Oct 6 at Sacramento State; Oct 12 at Idaho State; Oct 19 vs. UC Davis; Nov 2 vs. Montana State; Nov 9 at North Dakota; Nov 17 at Northern Arizona; Nov 23 vs. Cal Poly, 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.