Poker Stars $100+$9 No Limit Hold’em Tournament – t30/t60 Blinds – 9 players
TournamentPokerEdge.com Hand History Converter
UTG+1: t14000 233.33 BBs
UTG+2: t19318 321.97 BBs
MP1: t15955 265.92 BBs
MP2: t12674 211.23 BBs
Hero (CO): t13708 228.47 BBs
BTN: t14760 246 BBs
SB: t14240 237.33 BBs
BB: t14930 248.83 BBs
UTG: t15415 256.92 BBs
Pre Flop: (t90) Hero is CO with A A
2 folds, UTG+2 raises to t180, MP1 calls t180, MP2 calls t180, Hero raises to t780, 3 folds, UTG+2 calls t600, MP1 calls t600, MP2 calls t600
Flop: (t3210) 5 K A (4 players)
UTG+2 checks, MP1 checks, MP2 checks, Hero bets t1560, UTG+2 calls t1560, MP1 folds, MP2 calls t1560
Turn: (t7890) 8 (3 players)
UTG+2 checks, MP2 checks, Hero ????
is there ever a case for checking this turn back?
villains are standard fish who call smaller bets light but fold alot of turns and rivers.
you can make an argument for checking back but i htink given the fact they all called such a huge raise pre and 2/3 check called flop somebody has a big hand here and your likely to get a stack in..
i like betting ~3100 on turn leaving you ~9k to pile river…if just one of them calls pot will be 13k on river and give u a perfect bet size, and if both of them call even better because i dont see how your not getting it in on river
i think checking turn here is costing you significant value…….if the positions where flipped and u were first i think we can check here or flop and likely get a stack in as well
Most Users Ever Online: 2780
Currently Online:
56 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