NL25-NL50 2Bet PF and Call 3-Bet

NL25-NL50 2Bet PF and Call 3-Bet

Just want to make sure my Poker Tracker 4 stats aren't funky.

Looks like UTG in 9-Handed ring game with at least 50BB is calling with 60% of range after their 2bet was raised. That's amazing if true. Does anyone else have similar stats as mine?


10 July 2025 at 03:31 AM
Reply...

5 Replies


Earlier posts are available on our legacy forum HERE

Posting your stats here is the wrong way to approach this. Look at specific spots whether you are losing or winning on average. Depending on your sample size, you can either do specific positions or specific types of hands in specific positions. Then adapt your ranges based on that. You can also find play and explain content on youtube to see how they play and compare with your strategy.


I misread the thread, these are field reads. If so, yeah doesnt seem too inacurate


by GreatMorty

I misread the thread, these are field reads. If so, yeah doesnt seem too inacurate

Thanks for the reply. Seems like once a UTG player in this pool likes their hand they don't want to release it even after a 3-bet. Way too sticky.


You haven’t even shown your RFI % or your 2bet then 4bet% : you need the context of the data or it doesn’t really mean anything.


by CrazyAndy27s

You haven’t even shown your RFI % or your 2bet then 4bet% : you need the context of the data or it doesn’t really mean anything.

Interesting. What it means to me is that on average UTG player pool calls with 60% of the range they Raised with. I know that UTG RFI is around 10% and they 4bet after raising 12%

So when they are 3-bet they call 60% of their 10% range and raise 12% of it.

I believe a GTO opponent should fold 66% after getting 3-bet. But the player pool is only folding around 30%.

If that is the case we should probably change our 3-bet range to be more value oriented and less polarized.

I just was surprised that my online competition is looser and more passive than I gave them credit for and I just wanted to make sure that I wasn't misreading the stats.

Reply...