September 14, 2014
#Game No : 808935523
***** 888poker Hand History for Game 808935523 *****
$500/$1,000 Blinds No Limit Holdem – ***
Tournament #76533216 $5.45 + $0.55 – Table #19 9 Max (Real Money)
Seat 7 is the button
Total number of players : 9
Seat 1: Pokeroid_KI ( $12,368 )
Seat 2: jpt42 ( $44,062 )
Seat 3: turtlek1 ( $47,522 )
Seat 4: tupacalips ( $47,289 )
Seat 5: Katani7000 ( $69,664 )
Seat 6: grosve ( $12,543 )
Seat 7: joel1921 ( $29,958 )
Seat 9: Boysey18 ( $25,931 )
Seat 10: london_ace ( $78,208 )
jpt42 posts ante [$125]
Pokeroid_KI posts ante [$125]
turtlek1 posts ante [$125]
grosve posts ante [$125]
tupacalips posts ante [$125]
london_ace posts ante [$125]
joel1921 posts ante [$125]
Katani7000 posts ante [$125]
Boysey18 posts ante [$125]
Boysey18 posts small blind [$500]
london_ace posts big blind [$1,000]
** Dealing down cards **
Dealt to london_ace [ A, 3 ]
Pokeroid_KI folds
jpt42 folds
turtlek1 folds
tupacalips raises [$2,000]
Katani7000 folds
grosve folds
joel1921 folds
Boysey18 folds
london_ace calls [$1,000]
** Dealing flop ** [ A, J, 3 ]
london_ace checks
tupacalips bets [$2,812]
london_ace??
hey
no reads.
thoughts on which line we should take here? i think c/r is probably is the best line to take. If we c/r we may get value from Ax and some big pocket pairs like QQ if there’s any in there range. One reason as to why i also like c/c here is (also leading or c/r turn)because we hold the A we block combo’s of v having flush draws in their range also if we c/c v is likely going to bet their Ax hands anyway so we also get value by c/c here, stacks are not that deep either so its likely we can get all the money in the pot by c/c flop and then c/r turn if v does bet turn that is ,since he’s likely going to call a shove with a hand like AQ once they’ve bet turn.
another reason as to why i like c/r flop is that if v does have an ace then we may as well get value from it and if he does not then i’m not to sure if he’s going to barrel here with a hand like QT/KT. overall though i think c/r is more better then c/c. If i had a hand like K Q I’d go for a c/r here for sure or with any flush draw tbh. so yeah this is a spot where i’d be c/r my value/bluff hands for balance. I’d c/c with Ax and Jx , probably fold 99/88. If we c/r flop v may decide to shove over the top otf with a hand like AQ/AK or maybe even AT if he thinks our range is weight towards draws so im actually liking c/r flop more and more.
cheers.
cheers.
TPE Pro
December 6, 2012
I think c/r any flush draw here would be a pretty big mistake. This is a board that favors the PFR. You also have a hand that is very good for slowplaying. Unlike 33, you block your value target, and you also don’t have to worry about a flush card rolling off because even if it does you will still have a strong hand. I think slowplaying should definitely be the default here, and your opponent should be doing a fair bit of barreling as well as value betting worse on the turn. If you have good reason to think he won’t, then I can see k/r flop making sense, but I think you need a read to justify that.
September 14, 2014
Agreed.
if v had opened from LP do you think this flop would favor them? because if v is raising a wide range from LP c/r flops like this with a draw can’t be bad since v will be folding often as its hard to make a strong hand when you’re playing a wider range of hands. Hope that makes sense?
so basically c/r flops with our draws more rather then to an opponent that has opened in EP.
Most Users Ever Online: 2780
Currently Online:
79 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
bennymacca: 2616
Foucault: 2067
folding_aces_pre_yo: 1133
praetor: 1033
theginger45: 924
P-aire 146: 832
Turbulence: 768
The Riceman: 731
duggs: 591
florianm1: 588
Newest Members:
Tillery999
sdmathis89
ne0x00
adrianvaida2525
Anteeater
Laggro
Forum Stats:
Groups: 4
Forums: 24
Topics: 12705
Posts: 75003
Member Stats:
Guest Posters: 1063
Members: 12008
Moderators: 2
Admins: 5
Administrators: RonFezBuddy, Killingbird, Tournament Poker Edge Staff, ttwist, Carlos
Moderators: sitelock, sitelock_1