View Full Version : AK in multipay pot preflop
CourtesyFlush
11-22-2005, 12:02 AM
Kind of a basic question, but should you be more or less likely to reraise AK preflop in a multiway pot? I have spent most of my time playing NL online shorthanded. I tried playing some 10 handed tables a couple days ago I found myself in a couple situations where the UTG raised the pot (no read on him, not sure of his raising standards) and about 3-4 players called in front of me who I believe are rather loose. Should I just call here because I don't want to bloat the pot with a hand that is basically drawing at the flop, or reraise to take advantage of all of the dead money and take the initiative? I know what I prefer, but I wanted to check and see what the general consensus is.
CF
Since you're in position, raise. Knock out some of the limpers.
xorbie
11-22-2005, 12:10 AM
Depends very, very, veyr heavily on UTG.
CourtesyFlush
11-22-2005, 12:37 AM
[ QUOTE ]
Depends very, very, veyr heavily on UTG.
[/ QUOTE ]
Sorry I meant to add:
Assume zero read on UTG's raising standards, but you know all of the callers are rather loose calling preflop raises.
*Edit* I guess I did state that, refer to post below.
CourtesyFlush
11-22-2005, 12:41 AM
[ QUOTE ]
Depends very, very, veyr heavily on UTG.
[/ QUOTE ]
Can you tell me what your play would be if you knew UTG was:
1) a tight solid player
2) a loose raising donkey
3) a very passive preflop weak tight player
?
DoomSlice
11-22-2005, 12:51 AM
I almost always will raise here with AKo, and call with AKs. I just absolutely want to get it HU with UTG.
xorbie
11-22-2005, 01:00 AM
[ QUOTE ]
[ QUOTE ]
Depends very, very, veyr heavily on UTG.
[/ QUOTE ]
Can you tell me what your play would be if you knew UTG was:
1) a tight solid player
2) a loose raising donkey
3) a very passive preflop weak tight player
?
[/ QUOTE ]
1) I would raise here and try to pick it up on the flop no matter what it is.
2) I might call if he's too agressive preflop.
3) This could go to a fold even.
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.