top of page

SUBSCRIBE TO ESP NEWS

Inside the Numbers of Trevor Lawrence


On Saturday, Sunshine Lawrence will get his first start as a collegiate quarterback against Syracuse in Death Valley. With no more Kelly Bryant, a much heavier portion of the workload will now be cast on the young prodigy.

Through the Tigers first four games, Lawrence split time with Kelly Bryant but on Monday he was named the starter for Saturday's game. In his Tuesday press conference, Dabo Swinney said, "After four games, productivity and just the sheer data, he deserves to run out there first...this game."

Since 'data' played a seemingly big role in making this decision, let's take a look inside some of the numbers that ultimately gave Trevor Lawrence the starting job for Clemson.

 

So far this season, Lawrence has completed 39/60 passes for 600 yards, NINE touchdowns and TWO interceptions. He is averaging 10 yards per attempt and 150 yards per game.

The second quarter of games have been his most productive as he has thrown for 444 yards on 24/37 passing with SIX touchdowns and ONE interception.

He has also been extremely efficient on third downs, completing 10/14 passes for 197 yards, ONE touchdown and no interceptions. NINE of his 10 completions resulted in a first down - FIVE of them going for 15+ yards and THREE going for 25+ yards.

Second downs have also been very productive for the freshman. He has completed 14/23 passes on second downs for 202 yards and FOUR touchdowns. His two interceptions have also come on second down plays but neither were completely his fault.

[stats via CFBstats.com; click link for full breakdown]

According to College Football Film Room, Lawrence has been under pressure 11 times, hurried SEVEN times and sacked just twice in four games. He has been hit twice and had receivers drop FOUR passes from him.

I did my own personal analysis of how well Lawrence has thrown the deep ball through four games. You can find those stats by clicking this link.

199 views

Comments

Couldn’t Load Comments
It looks like there was a technical problem. Try reconnecting or refreshing the page.
bottom of page