2/5 - Should we be stacking of pre w/ AK for 100bb vs unknowns?

2/5 - Should we be stacking of pre w/ AK for 100bb vs unknowns?

Obviously it will depend, but here's a hand I had for example.

2/5, most of the table unknown, I've been here a few orbits and have had to fold to two 3-bets already, and once postflop after calling a 3B w/ AQs.
Villain (has not yet been in a hand w/ me) is middle aged white guy, certainly a rec, has raised preflop a few times, playing about 600, hero covers.

One limper, V in CO makes it 25, hero in SB with AKdd raises to 100, limper folds, V pretty quickly clicks it back to 225, hero...?

18 March 2025 at 10:20 AM
Reply...

13 Replies


Earlier posts are available on our legacy forum HERE

Without specific info, I usually ggi pre for ~100b with AK.

In this case, the 4bet size looks pretty good actually: it might be a coincidence, but I would tend to think that V knows what he's doing and his 4bet range is wider than KK+ .
So yes, I'd definitely shove.


by Niemand

In this case, the 4bet size looks pretty good actually: it might be a coincidence

Yeah I know, but based on appearance and vibe I'm sticking with a definite recerational


Get the money in. Yes V may be a rec but his sizings seems fine, yes you might expect him to call a lot of 3bets, but it is CO vs SB and therefore quite wide. You can't really call any hands here OOP, so it's jam or fold and you can't just be ripping QQ+ here. By all means if you want to make a very tight fold with some portion of your AKo then go ahead, the limper will tighten up CO range but AK is still plenty strong enough to jam. All the usual AK specific attributes apply (blocks AA and KK and is in good shape against every other hand, and has good fold equity against many of the hands it's behind ie medium pairs)


Are people really 4betting wide in live 2/5? My guess would be no - AK even against TT+ is 40%, so you need him to 4bet AQ at least to make this worth getting in. The main value from 3bing AK is when they call with inferior hands and you go to a flop dominating them with a larger pot. 4b ranges in live low stakes like this is usually nutty so I would fold readless.


by epine

Yeah I know, but based on appearance and vibe I'm sticking with a definite recerational

Could be a V used to tourney play with that sizing? Would explain both reads. Getting it in AP. (Edit, for reasons moxterite explained well above.) Nh.


This is a really close spot IMO. Villain has put in more than 1/3 of his stack, so there is no fold equity here. I don't think this is ever a bluff and I also think a hand like AKo is more likely to 4bet jam at this stack depth.

If we assume Villain is never folding, you should basically treat the 4bet as a jam. If you put the rest of the money in, you are wagering $500 to win a final pot of $1200, so you need 41.67% equity. AKs has 41.9% equity against QQ+ AK. Is he likely to be wider than that? If so, you should call (but I doubt it). Is he likely to be tighter than that? If so, you should fold.

I don't think jamming here is a mistake in a vacuum but it is a close spot.

Edit: If Villain had actually 4bet jammed here, I would be more likely to call because I think it weights his range more towards hands like AKo and JJ.


by pokerfan655

Are people really 4betting wide in live 2/5? My guess would be no - AK even against TT+ is 40%, so you need him to 4bet AQ at least to make this worth getting in. The main value from 3bing AK is when they call with inferior hands and you go to a flop dominating them with a larger pot. 4b ranges in live low stakes like this is usually nutty so I would fold readless.

That assumes CO is going to call a shove with hands like TT and AK. If we jam and get folds from these hands we are printing.


by Dan GK

Villain has put in more than 1/3 of his stack, so there is no fold equity here..

Good point, I hadn't spotted this.


It's close. I don't think we have any fold equity. When V is IP, I'd think he'd have more flats with hands like TT/JJ. Maybe he thinks we're getting OOL by 3B'ing too much of our range, or he's just hoping we fold, so he's 4B'ing wider. I'd probably just GII, but I'm not hating on anyone for finding the fold at low stakes.


Considering H has folded to pressure a few times, I probably just gii, but I don't mind a fold vs. a middle-aged rec. He rarely has worse than JJ here.


In general at 2-5 you want to 3bet wide enough that AKo is value.

Positions and reads etc. matter ... there are almost none here.
What is "a few orbits" ... having faced 3 3bets isn't a small amount. Do a bunch of players think you are the spot because you are opening super wide?

AQs hand could be anywhere from normal to bad.

Having a limper in a game with so many 3bets is pretty weird.

V's open is pretty big, his 4bet is either genius sizing or a fish with AA.
Your 3bet OOP is pretty big vs. "the rec." making it 5x.


by illiterat

What is "a few orbits" ... having faced 3 3bets isn't a small amount. Do a bunch of players think you are the spot because you are opening super wide?

Three orbits — which, being so few orbits, makes it impossible to say much of anything. Who knows what they think, or how they play. It doesn't feel like a super aggressive game, and I'm inclined to think that the 3B's indiciate a higher than usual proportion of premium hands, but obviously can't be sure.

by illiterat

V's open is pretty big, his 4bet is either genius sizing or a fish with AA.
Your 3bet OOP is pretty big vs. "the rec." making it 5x.

5x open over a limper is totally standard (for live games).
4x 3B when OOP is also totally standard.


by epine

...5x open over a limper is totally standard (for live games).
4x 3B when OOP is also totally standard.

Their open seems a tad high, but the argument is 20 vs 25 lol. Your 3! is as standard as it gets.

I have no idea how to interpret the same V 5x'ing in CO over a limper, and now getting tourney-clever by 2.2-ing it. Other than to jam, and make them figure it out. It's a bluff, but not an outrageous one. Calling doesn't sound good either.

For 100bb, sorry you lost. Shrug.

Reply...