I agree with whoever said thanks for all the updates. There's a bunch if us who don't watch college football and are soaking up everything you post. It's appreciated.

---

Season Ticket holder since 2004.

 

        

https://mobile.twitter.com/mathbomb/stat...4985596928

---

"Before you criticize a man, walk a mile in his shoes. That way, if he gets angry, he's a mile away and barefoot."

I know many of us like Duke Mayweather's oline breakdowns a lot so y'all might like his combine updated OL ranks.

https://twitter.com/BigDuke50/status/970108720293310464

---

I agree with whoever said thanks for all the updates. There's a bunch if us who don't watch college football and are soaking up everything you post. It's appreciated.

No problem guys. I’ve been in and out of the house all day so I’m doing my best from my phone.

---

"Before you criticize a man, walk a mile in his shoes. That way, if he gets angry, he's a mile away and barefoot."

Lamar Jackson look like crap, worse than Blake with regards to accuracy and ball placement. Pass.

---

I’d take Mason Rudolph in the 2nd to backup Blake and be groomed as a potential starter. Give me Hurst or a OG in the 1st.

---

What do yall think of Connor Williams at this point?  Kind of the forgotten man on the oline imo.  After the horrible combine by Brown, the beast performances by Nelson and Will. After his down year and could of been a top 10 pick a year ago, where do yall think would be good value?  Any chance he falls to our 2nd pick?  A decent combine imo just by looking at the numbers.  Khnarnn or Jack City it seems like yall watched most of the combine what do you guys think about Williams at RG year 1 and then take over for Parnell next year?  Seems like the only guy no one talking about

Hard to get a read on him. The Oline guys seemed fairly down on him at tackle but seems like there's been a big surge of him being good at guard. Tested well. I didn't like him but he's not bad.

Don't think he'll make it to the 2nd but your plan would work perfect.

---

My football player rankings so far:

Top QB
Josh Allen - Wyoming
Kyle Lauletta - Richmond
Mike White - Western Kentucky
Mason Rudolph - Oklahoma State
Josh Rosen - University of California - Los Angeles

Top RB
Kalen Ballage - Arizona State
Jaylen Samuels - North Carolina State
Saquon Barkley - Penn State
Rashaad Penny - San Diego State
Derrius Guice - Louisiana State

Top WR
Calvin Ridley - Alabama
D. J. Chark - Louisiana State
Anthony Miller - Memphis
Michael Gallup - Colorado State
Alan Lazard - Iowa State

Top TE
Mark Andrews - Oklahoma
Ian Thomas - Indiana
Ryan Izzo - Florida State
Dallas Goedert - South Dakota State
Hayden Hurst - South Carolina

Top OT
Conner Williams - Texas
Brian O'Neill - Pittsburgh
Kolton Miller - University of California - Los Angeles
Jamarco Jones - Ohio State
Mike McGlinchey - Notre Dame

Top OG
Will Hernandez - University of Texas - El Paso
Isaiah Wynn - Georgia
Quenton Nelson - Notre Dame
James Daniels - Iowa
Austin Corbett - Nevada

Top C
Frank Ragnow - Arkansas
Billy Price - Ohio State
Sean Welsh - Iowa
Will Clapp - Louisiana State
Mason Cole - Michigan

---

I’d take Mason Rudolph in the 2nd to backup Blake and be groomed as a potential starter. Give me Hurst or a OG in the 1st.

I like this plan. Hurst, Gesicki, or OG

---

IT WAS ALWAYS THE JAGS

Shaquem Griffin with a 4.38u 40.

Yeah you read that right. If it holds up it’s a combine record for linebackers.

---

"Before you criticize a man, walk a mile in his shoes. That way, if he gets angry, he's a mile away and barefoot."

Shaquem Griffin with a 4.38u 40.

Yeah you read that right. If it holds up it’s a combine record for linebackers.

I’d love to have him on the Jags. He, Myles, and Telvin would be the fastest LB group of all time lol.

---

I hope we draft him. We could use another LB and he’s a good one.

---

https://twitter.com/JUNGLECAT2017/status...2663461898

---

https://twitter.com/JUNGLECAT2017/status...2663461898

That regularly happens. His official time is 4.38.

---

https://twitter.com/JUNGLECAT2017/status...2663461898

Trolling again I see. They did the simulcast with Julio, Zeke, Barkley, and Sherman. Guess who won?

---

"Before you criticize a man, walk a mile in his shoes. That way, if he gets angry, he's a mile away and barefoot."

https://twitter.com/JUNGLECAT2017/status...2663461898

Trolling again I see. They did the simulcast with Julio, Zeke, Barkley, and Sherman. Guess who won?

Hey now. You can go You Tube the run and adjust the settings to the slowest replay, like quarter speed. It's clear the clock stopped at 4.38. He had two yards left to travel. Numerous other people mention the clock was stopped too early to give him a 4.38, the same speed as his twin ran last year.

The NFL Network simply made a few adjustments to his speed or to the speed of the other subjects to achieve sync.

I hand timed him myself and got 4.63 which is very similar to the time of his second run. This was very subjective manual timing.

Alas, I decided to determine the exact speed using the NFL video posted on You Tube.

You may not know this, but You Tube presents videos formatted at 30 frames per second. I counted the entire run from the moment of motion forward to the exact frame where his foot toes the finish line.

So you understand, I did a frame by frame measure using the You Tube time counter. I got just slightly under five seconds.

You can verify me, if you please.

Go to You Tube and find the forty. Pause the video. While the video is paused, you can hit the left arrow to move the video backwards several seconds at a time. Likewise, you can hit the right arrow on your keyboard and move the video several seconds forward. When you seemingly have the video close to were he breaks out of the starting block, use the comma key and the period key to advance the video one frame at a time.

If you hit the period key thirty times the video will advance one second forward. Remember you are counting the frames yourself. For every thirty times you tap the period key you are moving time forward one second.

I decided to provide you reference points to aid you.

Here are landmarks:

1 second - Two yard line
2 seconds - Nine yard line
3 seconds - Nineteen yard line
4 seconds - Thirty yard line


4 seconds PLUS (Since thirty frames equals one second 15 frames equals 0.5 seconds)

15 frames - thirty-six yard line  (15 frames equals 0.50 seconds)
25 frames - Toe on finish line (25 frames equals 0.83 seconds)

So using the You Tube video and counting out seconds thirty frames at a time, he ran a 4.83 forty. 

Please don't trust me. Test if for yourself.

---

Trolling again I see. They did the simulcast with Julio, Zeke, Barkley, and Sherman. Guess who won?

Hey now. You can go You Tube the run and adjust the settings to the slowest replay, like quarter speed. It's clear the clock stopped at 4.38. He had two yards left to travel. Numerous other people mention the clock was stopped too early to give him a 4.38, the same speed as his twin ran last year.

The NFL Network simply made a few adjustments to his speed or to the speed of the other subjects to achieve sync.

I hand timed him myself and got 4.63 which is very similar to the time of his second run. This was very subjective manual timing.

Alas, I decided to determine the exact speed using the NFL video posted on You Tube.

You may not know this, but You Tube presents videos formatted at 30 frames per second. I counted the entire run from the moment of motion forward to the exact frame where his foot toes the finish line.

So you understand, I did a frame by frame measure using the You Tube time counter. I got just slightly under five seconds.

You can verify me, if you please.

Go to You Tube and find the forty. Pause the video. While the video is paused, you can hit the left arrow to move the video backwards several seconds at a time. Likewise, you can hit the right arrow on your keyboard and move the video several seconds forward. When you seemingly have the video close to were he breaks out of the starting block, use the comma key and the period key to advance the video one frame at a time.

If you hit the period key thirty times the video will advance one second forward. Remember you are counting the frames yourself. For every thirty times you tap the period key you are moving time forward one second.

I decided to provide you reference points to aid you.

Here are landmarks:

1 second - Two yard line
2 seconds - Nine yard line
3 seconds - Nineteen yard line
4 seconds - Thirty yard line


4 seconds PLUS (Since thirty frames equals one second 15 frames equals 0.5 seconds)

15 frames - thirty-six yard line  (15 frames equals 0.50 seconds)
25 frames - Toe on finish line (25 frames equals 0.83 seconds)

So using the You Tube video and counting out seconds thirty frames at a time, he ran a 4.83 forty. 

Please don't trust me. Test if for yourself.

Galaxy brain here.  

Imagine being so monumentally dumb that you think your measurements are more accurate than the ACTUAL laser timed scores.

---

Hey now. You can go You Tube the run and adjust the settings to the slowest replay, like quarter speed. It's clear the clock stopped at 4.38. He had two yards left to travel. Numerous other people mention the clock was stopped too early to give him a 4.38, the same speed as his twin ran last year.

The NFL Network simply made a few adjustments to his speed or to the speed of the other subjects to achieve sync.

I hand timed him myself and got 4.63 which is very similar to the time of his second run. This was very subjective manual timing.

Alas, I decided to determine the exact speed using the NFL video posted on You Tube.

You may not know this, but You Tube presents videos formatted at 30 frames per second. I counted the entire run from the moment of motion forward to the exact frame where his foot toes the finish line.

So you understand, I did a frame by frame measure using the You Tube time counter. I got just slightly under five seconds.

You can verify me, if you please.

Go to You Tube and find the forty. Pause the video. While the video is paused, you can hit the left arrow to move the video backwards several seconds at a time. Likewise, you can hit the right arrow on your keyboard and move the video several seconds forward. When you seemingly have the video close to were he breaks out of the starting block, use the comma key and the period key to advance the video one frame at a time.

If you hit the period key thirty times the video will advance one second forward. Remember you are counting the frames yourself. For every thirty times you tap the period key you are moving time forward one second.

I decided to provide you reference points to aid you.

Here are landmarks:

1 second - Two yard line
2 seconds - Nine yard line
3 seconds - Nineteen yard line
4 seconds - Thirty yard line


4 seconds PLUS (Since thirty frames equals one second 15 frames equals 0.5 seconds)

15 frames - thirty-six yard line  (15 frames equals 0.50 seconds)
25 frames - Toe on finish line (25 frames equals 0.83 seconds)

So using the You Tube video and counting out seconds thirty frames at a time, he ran a 4.83 forty. 

Please don't trust me. Test if for yourself.

Galaxy brain here.  

Imagine being so monumentally dumb that you think your measurements are more accurate than the ACTUAL laser timed scores.

It's not rocket science.

---

It’s the same timing mechanism for all the runners. He was still nearly a tenth faster than any other LB at the combine this year even with your secondary calculations. Watching every player run it was clear who was the fastest.

---

Trolling again I see. They did the simulcast with Julio, Zeke, Barkley, and Sherman. Guess who won?

Hey now. You can go You Tube the run and adjust the settings to the slowest replay, like quarter speed. It's clear the clock stopped at 4.38. He had two yards left to travel. Numerous other people mention the clock was stopped too early to give him a 4.38, the same speed as his twin ran last year.

The NFL Network simply made a few adjustments to his speed or to the speed of the other subjects to achieve sync.

I hand timed him myself and got 4.63 which is very similar to the time of his second run. This was very subjective manual timing.

Alas, I decided to determine the exact speed using the NFL video posted on You Tube.

You may not know this, but You Tube presents videos formatted at 30 frames per second. I counted the entire run from the moment of motion forward to the exact frame where his foot toes the finish line.

So you understand, I did a frame by frame measure using the You Tube time counter. I got just slightly under five seconds.

You can verify me, if you please.

Go to You Tube and find the forty. Pause the video. While the video is paused, you can hit the left arrow to move the video backwards several seconds at a time. Likewise, you can hit the right arrow on your keyboard and move the video several seconds forward. When you seemingly have the video close to were he breaks out of the starting block, use the comma key and the period key to advance the video one frame at a time.

If you hit the period key thirty times the video will advance one second forward. Remember you are counting the frames yourself. For every thirty times you tap the period key you are moving time forward one second.

I decided to provide you reference points to aid you.

Here are landmarks:

1 second - Two yard line
2 seconds - Nine yard line
3 seconds - Nineteen yard line
4 seconds - Thirty yard line


4 seconds PLUS (Since thirty frames equals one second 15 frames equals 0.5 seconds)

15 frames - thirty-six yard line  (15 frames equals 0.50 seconds)
25 frames - Toe on finish line (25 frames equals 0.83 seconds)

So using the You Tube video and counting out seconds thirty frames at a time, he ran a 4.83 forty. 

Please don't trust me. Test if for yourself.

https://mobile.twitter.com/rapsheet/stat...7707858950

---

"Before you criticize a man, walk a mile in his shoes. That way, if he gets angry, he's a mile away and barefoot."