SCOOP-31-H (Sunday Million $530) : facing C4bet with AKo 100bb effective

Posted by

Posted by posted in High Stakes

SCOOP-31-H (Sunday Million $530) : facing C4bet with AKo 100bb effective

Blinds: t500/t1,000 (9 Players) CO: 99,278 (Hero)
BN: 116,000
SB: 101,790
BB: 70,221
UTG: 158,050
UTG+1: 62,758
MP: 112,100
MP+1: 184,450
MP+2: 93,975
UTG is TAG-ish player and BTN and MP are unknown.
UTG : 16/13/5 (141h)
MP : 19/15/15 (26h)
BTN :19/19/16 (26 hands)
Preflop (1,500) Hero is CO with K A
UTG raises to 2,400, UTG+1 folds, MP calls 2,400, 2 folds, Hero raises to 10,350, BN raises to 24,000, 2 folds, UTG folds, MP folds, Hero calls 13,650
My question is how should I approach this spot?
I am not familiar with C4bet pot in high stackes tournement.
My intuition would be to :
- eventually fold against a nitty player
- 5bet shove something like KK, AKs
- call AKo, AJs+, JJ-QQ, AA. I am not very sure about KQs espacially against this sizing.
What do you think ?
Should I just jam AKo or simply fold as a default ?

3 Comments

Loading 3 Comments...

Rapha Nogueira 6 years, 10 months ago

Call pre, except with very strong reads that UTG and MP are way too wide. Calling seems pretty bad OOP with no implied odds against the hands we are flipping against. 3bet-folding seems the best as played.

belgianbeer 6 years, 10 months ago

I cannot imagine that the EV of calling pre > of squeezing even if against EP ranges.
isolate IP with AK seems mandatory in my opinion with 100bb.
3bet avoid us to play MWP, reduce the SPR and enjoy the fold equity.
Also it allows us to play IP with initiative in big pot which is a very high EV outcome.
where cold call might induce several other calls, which is very bad for this kind of holding.
Also if we face a squeeze after cold calling we will be forced to 4bet-jam and play for stack with equity around 35-40% when we get called (as I dont expect any AQo- to call us).
I really cannot imagine calling > 3bet

Be the first to add a comment

Runitonce.com uses cookies to give you the best experience. Learn more about our Cookie Policy