Welcome to PatsFans.com

QB Hurries chart

Discussion in 'PatsFans.com - Patriots Fan Forum' started by PushnPencils, Aug 3, 2011.

Thread Status:
Not open for further replies.
  1. PushnPencils

    PushnPencils Rookie

    Joined:
    Mar 3, 2007
    Messages:
    948
    Likes Received:
    1
    Ratings:
    +1 / 0 / -1

  2. Zach004265

    Zach004265 Rookie

    Joined:
    Jan 10, 2010
    Messages:
    4
    Likes Received:
    0
    Ratings:
    +0 / 0 / -0

    So is tully and he is even higher than roth! So I dont know if I trust these rankings.
  3. AndyJohnson

    AndyJohnson PatsFans.com Veteran PatsFans.com Supporter

    Joined:
    Sep 13, 2004
    Messages:
    22,115
    Likes Received:
    75
    Ratings:
    +252 / 13 / -8

    Tough stat. Ive seen Raheem Brock listed elsewhere with 38 hurries and he isnt even on that list.
    I've seen Roth listed as leading the league also.
    As far as TBC, thats exactly the problem, he couldn't get there quick enough to do any more than cause a rush.
    Sometimes a rush is a great play turning blocked into pressure. Sometimes its not, turning a sack or hit into a hurry.
  4. Sciz

    Sciz PatsFans.com Supporter PatsFans.com Supporter

    Joined:
    Jul 13, 2009
    Messages:
    7,209
    Likes Received:
    87
    Ratings:
    +200 / 2 / -0

    The link is only through 12 weeks. And 38 was Brock's sacks+hits+hurries, where the link is just hurries.
  5. AndyJohnson

    AndyJohnson PatsFans.com Veteran PatsFans.com Supporter

    Joined:
    Sep 13, 2004
    Messages:
    22,115
    Likes Received:
    75
    Ratings:
    +252 / 13 / -8

    I'm pretty sure someone posted Brock having 38 hurries
  6. Sciz

    Sciz PatsFans.com Supporter PatsFans.com Supporter

    Joined:
    Jul 13, 2009
    Messages:
    7,209
    Likes Received:
    87
    Ratings:
    +200 / 2 / -0

    I know I used that number, but not for hurries. 9 sacks, 10 hits, 19 hurries, 38 total pressures.
Thread Status:
Not open for further replies.

Share This Page

unset ($sidebar_block_show); ?>