• Follow us on Twitter @buckeyeplanet and @bp_recruiting, like us on Facebook! Enjoy a post or article, recommend it to others! BP is only as strong as its community, and we only promote by word of mouth, so share away!
  • Consider registering! Fewer and higher quality ads, no emails you don't want, access to all the forums, download game torrents, private messages, polls, Sportsbook, etc. Even if you just want to lurk, there are a lot of good reasons to register!

RB Ezekiel Elliott (All B1G, All-American, National Champion, Pro Bowl, All Pro, Dallas Cowboys)

Jump to latest Follow Reply
Sort by date Sort by votes
MililaniBuckeye said:
The Game this past season, on his long run in the first quarter.
Click to expand...

Actually he was clipped by a Michigan defender within 5 or so yards of the LOS (I think it was Bolden, but I may not be remembering that correctly). There's a big difference between getting caught from behind and having a defender catch up to you because you've lost your momentum due to taking a hit. I wouldn't at all call Zeke's long run against Michigan a case of "getting caught from behind."
 
Upvote 0
buckeyesin07 said:
Actually he was clipped by a Michigan defender within 5 or so yards of the LOS (I think it was Bolden, but I may not be remembering that correctly). There's a big difference between getting caught from behind and having a defender catch up to you because you've lost your momentum due to taking a hit. I wouldn't at all call Zeke's long run against Michigan a case of "getting caught from behind."
Click to expand...
He was still ahead of the two defenders that were chasing him when he got up to full speed...
 
Upvote 0
buckeyesin07 said:
By the time he got back to full speed, the defender had the angle on him. That run was not EE getting caught from behind.
Click to expand...
Uh, no. #22 even stumbled a bit at the OSU 36 while turning to chase Zeke. When Zeke was at the 50 #22 was a good yard behind and two yards to Zeke's right. And if you remember your trigonometry, Zeke was running the B side while #22 was running the C side.

zeke-elliott-against-michigan.gif


Zeke-run-UM-screencap.png
 
Last edited:
Upvote 0
MililaniBuckeye said:
Uh, no. #22 even stumbled a bit at the OSU 36 while turning to chase Zeke. When Zeke was at the 50 #22 was a good yard behind and two yards to Zeke's right. And if you remember your trigonometry, Zeke was running the B side while #22 was running the C side.

zeke-elliott-against-michigan.gif


View attachment 12677
Click to expand...

You're confusing "getting tackled" with "getting caught from behind." It's too bad Zeke got clipped just a bit, because then you wouldn't be so confused (to say nothing of your clear lack of understanding of trig; protip: if you know very, very little about a subject, next time don't try to appeal to that subject in an attempt to support an argument you're making :lol:).
 
Last edited:
Upvote 0
That play captures Zeke's speed well. He's not a speed demon but he's also not a plodding tailback. Bradley Roby will track him down easily but your average safety will not.

It's his burst, feet, balance and vision that make him special, not his straight line speed. Derrick Henry has the speed and burst but not the rest.
 
Upvote 0
jwinslow said:
That play captures Zeke's speed well. He's not a speed demon but he's also not a plodding tailback. Bradley Roby will track him down easily but your average safety will not.

It's his burst, feet, balance and vision that make him special, not his straight line speed. Derrick Henry has the speed and burst but not the rest.
Click to expand...
^- this -^. My posts weren't meant to state that Zeke isn't fast, but rather he's not the blistering bullet some think, while at the same time debunking the moronic media observation that he "sometime gets caught from behind".
 
Upvote 0
You must log in or register to reply here.
Back
Top