Two Plus Two Newer Archives  

Go Back   Two Plus Two Newer Archives > PL/NL Texas Hold'em > Small Stakes
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Display Modes
  #1  
Old 04-13-2007, 08:11 PM
TenFourOff TenFourOff is offline
Senior Member
 
Join Date: Nov 2005
Posts: 121
Default $1/$2 NL live, flopped strong draw OOP.

I was down to $120 when this hand came up. CO was a respected regular, fairly tight. Need help on flop.

10 players, I was BB and dealt 5[img]/images/graemlins/diamond.gif[/img]5[img]/images/graemlins/heart.gif[/img], 3 limpers, CO raised to $10, folded to me, I called and the three limpers folded.
Flop ($25 in pot)4[img]/images/graemlins/club.gif[/img]6 [img]/images/graemlins/diamond.gif[/img]7 [img]/images/graemlins/spade.gif[/img]
I missed my set, but now I have a great draw and probable best hand, although quite vulnerable. What should I do? I was debating between betting pot, trying to CR, and pushing.
Reply With Quote
  #2  
Old 04-13-2007, 08:24 PM
downtown downtown is offline
Senior Member
 
Join Date: Dec 2004
Location: Chicago
Posts: 1,198
Default Re: $1/$2 NL live, flopped strong draw OOP.

what's your plan for the turn if you bet pot and miss? I don't like it.
check/call

edit: c/r is bad, pushing is horrible.
Reply With Quote
  #3  
Old 04-13-2007, 08:52 PM
TenFourOff TenFourOff is offline
Senior Member
 
Join Date: Nov 2005
Posts: 121
Default Re: $1/$2 NL live, flopped strong draw OOP.

If I bet the pot and miss, I would re-evaluate turn. I am most likely against overcards, with a small possibility I am against an overpair. If the turn is low, or pairs the board, I would likely pot turn.
If I was raised on the flop, I would probably push.
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 10:56 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.