FINAL Game forecast · REGULAR week 5
UCFatHouston
SharpTake projected Houston at 71%. Houston won.
Pregame forecast · published before kickoff and not revised
SharpTake projects Houston to win.
Why SharpTake leans
Why SharpTake leans Houston
Houston's overall quality is the biggest reason SharpTake favors Houston. Houston also has the edge in down-to-down efficiency and recent scoring performance, while UCF's record from last season pushes the other way.
Last season's results
Down-to-down efficiency
Recent scoring performance
On-field context
Matchup breakdown
These matchup factors describe where the teams differ on the field. They are separate from SharpTake's forecast explanation above.
Houston explosive plays
EDGEHouston creates big-play value on successful plays at a rate near the FBS middle, while UCF allows big-play value on successful plays far less often than most FBS teams. That comparison favors UCF.
Comparison basis · Explosiveness vs explosiveness allowed
Run game
NO EDGEHouston gains enough yardage on runs for the down and distance at a rate near the FBS middle, while UCF allows enough yardage on runs for the down and distance more often than most FBS teams. The evidence does not separate the teams enough for an advantage here.
Comparison basis · Rushing success rate vs rushing success rate allowed
Disruption
NO EDGEUCF avoids tackles for loss, passes defensed, and forced fumbles less often than most FBS teams, while Houston creates tackles for loss, passes defensed, and forced fumbles at a rate near the FBS middle. The evidence does not separate the teams enough for an advantage here.
Comparison basis · Havoc allowed vs havoc created
Explore
Go deeper
Team reads
Position rooms
Coverage and limitations
- Forecasts are produced only when both teams meet SharpTake's evidence requirements.
- Player availability, injuries, weather, travel, and rest are not included.
- Explain factors use completed 2025 team-season evidence. They describe matchup contrasts and are not causal model attribution.
Forecasts are model-based context, not guarantees.