• Fueling conversations and igniting meaningful experiences for cricket fans around the world
  • Fueling conversations, igniting experiences
last year

As a young captain I’d like to ask why the Gully position is popular for fast and medium pace bowlers. I tend to see more balls go the 3rd or 4 slip area and wondered should I be using them instead of gully?

Comments

Gully is at 45 degrees to the bat edge
4th slip is best comparison
2 gully’s is coming for a bat who plays with a open bat face
All about angles

Partner Sponsors

Responses

Hi Glen, you’ve obviously been given the captaincy for a reason. Go with your instincts, the only thing I will say is….. if your thinking about it do it straight away. The last thing you want is to see one fly through 3rd slip , and you where thinking I’ll change it next ball. Good luck mate

Always go with your gut feeling!
In saying that, really depends on the pitch. If a quick pitch maybe slips a better option if a slow pitch Gully could be a better option. Also worth considering is the type of batter on strike, a prodder slips might be a better option. If someone is going hard a gully could be better.

So many variables in this. It depends on the the pitch, batsman and type of bowler. You are the captain, go with your gut feeling. Whenever possible I like to have a natural left hander in the gully to a right hand batsman and a right hander at slip. That way the fielders strong side is covering the large gap between slip and gully, effectively making the gap smaller.

Glen, Good question! It’s hard to give a definitive answer. As a Capt you need to be adaptive to the pitch conditions, batting style, bowler pace etc.

I’ve always erred on the side on a finer gully to the fast bowlers and a squarer gully for the slower bowlers.

Just a thought, Why not 3 slips and a gully?

Your Answer

If you wish to include a video or audio response, you can do this by including links to Youtube, Vimeo or SoundCloud (https://www.youtube.com/watch?v=xxxxxxxxxx OR https://vimeo.com/xxxxxxxxx)

<% error.message %>