[NL5z] - Folding weakest flush on river
Posted by camikaze007
Posted by camikaze007 posted in Low Stakes
[NL5z] - Folding weakest flush on river
Blinds: $0.02/$0.05 (6 Players)
BN: $10.81 (Hero)
SB: $7.48
BB: $3.66
UTG: $15.22
MP: $5.00
CO: $6.89
SB: $7.48
BB: $3.66
UTG: $15.22
MP: $5.00
CO: $6.89
Villain is short stacked and is playing 33/33 over 22 hands, which trends towards a weaker player, but not enough hands to get a conclusive sample. Villain also has an AF of 0 (never made an aggressive postflop action) but again a very small sample.
Preflop
($0.07)
Hero is BN with
3
4
, , ,
34s is at the bottom of my opening range but with a trending weaker player in the BB this is a +EV open.
Flop
($0.26)
2
7
6
, ,
gutshot, fd and no SDV so this is a perfect bluffing candidate. We don't want to bet small with range as this board smacks BB range but we don't want to overbet because villain can have a lot of nutted hands so a 70% bet seems adequate.
Turn
($0.60)
2
7
6
8
, , ,
We make the flush and continue betting. BB effectively min raises and from a passive player and population tendencies this trends towards very nutted hands. I think villain will raise sets and 2pair+ OTF so this is either 87, 88, flushes or 9T. Should we be 3betting here?
River
($2.50)
2
7
6
8
T
,
Villain pots on the T river. With flushes and 4 to a straight I don't think villain will do this will 87 or 88 and his 9T combos just got reduced. Villain still has all his flushes. We need about 35% (after rake) to BE and if villain does this with his Add, Kdd, Qdd, Jdd and T9 we have about 39%; however I don't think villain bets all his T9 at this size with 100% frequency, instead preferring a smaller sizing/check as he chops with 9x, however this is a size that all flushes would use to get value from 9x.
Is my analysis sound? Was this fold too nitty?
Is my analysis sound? Was this fold too nitty?
Final Pot
BB wins $2.40
Rake is $0.10
Rake is $0.10
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.