NL25 overpair trying to extract

Posted by

Posted by posted in Low Stakes

NL25 overpair trying to extract

BN: $62.77
SB: $25.65 (Hero)
BB: $27.21
UTG: $26.96
HJ: $17.16
CO: $19.27
villain is 19/14/3 over 800 hands. Not very positionally aware. Probably can have some SCs in his pf range and all the pairs (fold to 3b IP 42%). 4b 15%, but he has showdown only KK+ and AK after 4betting.
Preflop ($0.35) (6 Players)
Hero was dealt A A
UTG raises to $0.50, HJ folds, CO folds, BN folds, Hero raises to $1.90, BB folds, UTG calls $1.50
Flop ($4.25) J 5 3 (2 Players)
Hero bets $2.50, UTG raises to $5, Hero calls $2.50
Turn ($14.25) 7 (2 Players)
We have 18.65$ behind

I'm not sure what's the best way to get the money in. I'm def not planning to fold on vast majority of runouts, I see villains showing up with goofy stuff way too often after taking these lines.

He can have some random QQ, but I dont expect to see that too often, since he is 4betting fair bit and isnt positionally aware. And sets. Against those hands, money is going in regardless of what I do. 

I've seen a lot of villains trying to mr IP w/ hands like Jx or 66-TT in order to get cheaper showdown/trying to stop me from barreling my equity. So I wanna focus on that range. He can also have random bluffs, but I'm not sure he is aware putting more money in with those.

I think that 3betting flop gets him to fold everything that isnt a "setup". So I think that calling his raise is ideal.

Since turn gets checked through a lot, I wanna donk, but I'm not sure about the sizing. Since he is likely drawing to 2-5 outs, does it make sense to bet turn really small? Like 4$? And jam the river? He is not a reg, so he might talk himself into calling twice.

Villain ended up not doing a mistake vs my line. I ended up betting 3.75$ ott and jamming river.

Thanks


Loading 1 Comments...

Be the first to add a comment

You must upgrade your account to leave a comment.

This thread has been locked. No further comments can be added.

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