Poker GTO HUD: Track Stats Against GTO Benchmarks (6-Max)

Author:Stray Cat
Published:
Updated:
Intermediate / Advanced

Poker GTO HUD: Track Stats Against GTO Benchmarks (6-Max)

For people searching poker gto hud: how to line up HUD stats with GTO benchmark bands, which metrics matter in 6-max, sample-size rules, and practice on nlh.poker.

This guide answers the search poker gto hud: how to line up HUD stats with GTO benchmark bands and spot baseline drift. For VPIP and PFR definitions, read VPIP & PFR basics. For GTO theory, see What Is GTO in Poker? first.

Typical reasons people search this phrase:

  • Check whether live HUD numbers match GTO frequencies from solvers or charts
  • Pick only the stats that matter for GTO study—not a 40-stat panel
  • Measure drift from an equilibrium baseline with objective numbers

Bottom line: put HUD frequencies next to GTO benchmark bands and see where you drift. In 6-max at roughly 100bb, a small set of core stats closes the gap between solver study and real hands.

What This Article Does Not Cover

  • Full stat definitions and opportunity counting → see VPIP/PFR and c-bet basics
  • Exploit adjustments by player type → Exploitative vs GTO
  • PokerTracker / HM3 HUD setup walkthroughs (this article focuses on stat selection and benchmarks)

Line Up GTO Benchmarks with HUD Stats

GTO gives you equilibrium-style target frequencies and ranges. HUD gives you live aggregates—VPIP, PFR, c-bet rate, and so on. Putting them side by side answers: "Theory says X%, but my game shows Y%."

  • GTO (yardstick): Solver output, charts, baseline thinking from GTO basics
  • HUD (measurement): Tracker or nlh.poker stats—see stats primer

Online HUDs often overlay villain stats. For GTO study, start with your own numbers on nlh.poker's statistics page. Do not mirror a 20–40 stat exploit panel; keep only what you need for baseline checks:

  • Baseline maintenance: Are you playing in a way opponents cannot auto-profit against?
  • Study alignment: Do your live frequencies match what you learned from charts and solvers?
  • Priority leaks: Which spots cost the most EV when you drift?

HUD for GTO Study vs HUD for Exploit Reads

Both use HUD stats like VPIP and flop c-bet, but the purpose differs.

AngleGTO study (baseline check)Exploit analysis
Primary targetYour baselineOpponent leaks
Stat count10–15 stats20–40+ stats
Decision axisSolver / theory bandsExtreme opponent numbers
Example"Is my flop c-bet too high?""Villain folds 65%+ to c-bet—bluff more"
Best stageBuilding a solid foundationAfter villain sample builds

As in GTO basics, play near GTO against unknown strong opponents; shift toward exploits when tendencies are clear. Match your stats to GTO bands first, then combine leak analysis when reading villains.

Essential Preflop Stats for GTO Study

Preflop is the easiest place to connect theory and HUD numbers. For 6-max at 100bb, track these first:

  1. VPIP: How wide you enter pots (definition)
  2. PFR: Raise frequency; gap vs VPIP flags over-calling
  3. RFI (Raise First In): Open-raise rate when action folds to you
  4. 3-bet: Re-raise frequency facing an open
  5. Fold to 3-bet: Fold rate vs 3-bets (IP/OOP split is ideal)
  6. Cold call: Flat calls after an open and caller(s)—too wide means OOP pain
  7. Squeeze: Re-raise after open + call(s) (optional, intermediate+)

Never judge from global VPIP/PFR alone when pairing GTO with HUD stats. BTN RFI near 43% with UTG RFI near 30% is a position leak worth fixing. See 6-max RFI ranges for position benchmarks.

Postflop Stats for GTO Baseline Checks

Postflop spots are more context-dependent than preflop, but these stats catch large deviations early:

  • Flop CB: C-bet rate as the preflop aggressor on the flop
  • Fold to CB: Fold rate vs c-bets (compare to MDF)
  • Turn CB / River bet: Barrel frequencies for range balance
  • WTSD / W$SD: Went to showdown and won at showdown (WTSD guide)
  • AF (Aggression Factor): (Bets + raises) ÷ calls—supporting metric only

Flop c-bet above 70% or below 40% often conflicts with board-aware frequencies from c-bet basics. Fold to c-bet that is too high may put you below MDF, letting opponents auto-profit with bluffs.

Preflop: VPIP 28% / PFR 22% (6-max overall)

Overall stats after 2,500 hands at 100bb 6-max. Participation is slightly high from CO and BTN.

Your hand
9♠8♥
Explanation

A 6-point gap between VPIP and PFR is reasonably aggressive. Global numbers alone cannot tell which positions are driving participation. Pair overall VPIP/PFR with position RFI. Here CO and BTN run slightly high—check whether weak offsuit connectors like the 98o in the diagram are being opened too often from CO, and whether RFI sits above benchmark bands.

Postflop: Flop CB 72% / Fold to CB 58%

Mostly single-raised pots where you were the preflop aggressor. Half-pot to two-thirds-pot c-bets are common.

Your hand
K♦Q♣
Board
7♠4♥2♦
Explanation

Flop c-bet above 70% is a classic over-c-bet pattern. Betting every board with marginal hands like KQo weakens your turn range and invites probes. Fold to c-bet at 58% may also fall below MDF on common sizes—a sign you are drifting from GTO on both offense and defense.

6-Max GTO Benchmark Ranges (100bb)

These are overall 6-max bands for ~100bb effective stacks and ~2.5bb opens. They summarize widely cited ranges from PokerCoaching, PokerStrategy, RiverOdds, GTO Gecko, and similar public training material; rake and lineup shift numbers a few points. Position and board breakdowns are more reliable than global averages. See references below the table for sources.

Stat6-max band (guide)Compare to GTO band
VPIP22–28%Above 30% may be too loose; below 18% may be too tight
PFR18–22%VPIP–PFR gap over 10 pts suggests over-calling
RFI (BTN)40–45%Cross-check with the RFI guide table
RFI (UTG)15–18%Are early positions tight enough?
3-bet7–10%Under 5% is passive; over 12% may be too aggressive
Fold to 3-bet50–55%70%+ may mean opens too wide or missing 4-bets; IP/OOP split is ideal
Flop CB55–65% (global guide)IP ~60–70%, OOP ~45–55%; board texture moves this a lot
Fold to CB40–48%58%+ is a common MDF leak; allowed fold rate depends on bet sizing
WTSD27–30%32%+ may mean going to showdown too often
W$SD50–55%Pair with WTSD—fighting too many pots with weak hands?

Treat these as a compass, not numbers to memorize. Fix the biggest outliers first—see EV loss and feasibility.

References (accessed 2026-07-06)

Sample Size Rules

Pairing GTO with HUD stats only works if you manage sample size. Required hands vary widely by stat:

StatRough sampleNote
VPIP / PFR500–1,000 handsStabilizes relatively fast
RFI / 3-bet1,000–3,000 handsMore if split by position
Flop CB / Fold to CB2,000–5,000 handsOpportunity-based—high variance
River stats5,000+ handsLow frequency—do not trust short samples

Concluding "80% flop c-bet means I over-c-bet" after a few hundred hands is risky. Gray out stats until sample is adequate. On nlh.poker, check hand counts on the stats page and verify flagged spots with hand review.

3 Steps to Spot Baseline Drift

Fix a monthly routine so you always know where to start when you open your stats:

  1. Check preflop entry: VPIP/PFR gap → position RFI → 3-bet and fold to 3-bet. Large gaps? Return to preflop ranges
  2. Check postflop balance: Flop c-bet vs fold to c-bet against MDF—is offense or defense extreme?
  3. Verify flagged stats in hands: Bookmark spots tied to red-flag numbers; compare to solvers or study articles

Break down which position and spot drives the leak—not just one global number. That clarifies priorities in your study routine.

Compare GTO Bands with Stats on nlh.poker

Even without third-party tracking software, nlh.poker's statistics page shows VPIP, PFR, position stats, and key postflop metrics after you play. To line them up with GTO benchmarks:

  • Weekly check: Every ~500 hands, review VPIP/PFR and RFI
  • Bookmark link: Save confusing 3-bet or c-bet hands; match decisions to stats
  • Article cluster: GTO theory → this guide (stat selection) → leak fixes

Free browser play with auto stats is ideal for baseline self-monitoring. See the stats section in nlh.poker app guide. For trainer tools, read GTO poker practice.

FAQ

What does poker gto hud mean?

It is not a fixed industry term. People usually search it when they want to check HUD frequencies against a GTO baseline—whether live stats match solver or chart targets. This guide shows how to compare VPIP, PFR, 3-bet, c-bet, and related stats to benchmark bands in 6-max.

How many HUD stats do you need for GTO study?

For 6-max cash study, 10–15 stats is enough: roughly 5–7 preflop and 4–6 postflop. Adding too many slows decisions and makes you react to unreliable small samples. Start with VPIP, PFR, 3-bet, fold to 3-bet, flop c-bet, and fold to c-bet.

Do HUD stats match solvers exactly?

No. HUD stats are live aggregates; solvers output theory for specific assumptions (rake, sizing, ranges). Use benchmarks as bands—are you roughly in range?—not as targets to hit to the decimal. Position and spot breakdowns matter more than global averages.

Can you track the same metrics outside online poker?

Live poker has no on-screen HUD, but you can track the same metrics in session notes or in a practice app stats page. Browser trainers like nlh.poker auto-collect stats while you play, which makes baseline monitoring much easier.

Does HUD use differ for GTO study vs exploit analysis?

Yes. GTO study starts with your own frequencies vs equilibrium targets. Exploit analysis emphasizes opponent leaks—high fold to c-bet, low 3-bet, and so on. Build your baseline first, then widen the HUD toward villain reads.

Summary

  • Line up HUD stats with GTO benchmark bands to measure equilibrium drift
  • Prioritize preflop: VPIP, PFR, RFI, 3-bet, fold to 3-bet
  • Postflop: flop c-bet, fold to c-bet, WTSD/W$SD for attack/defense balance
  • Use benchmark bands; do not overreact to small samples
  • nlh.poker stats plus hand review connect GTO study to real play

Stats are a map to your next leak to fix, not a script for perfect GTO. Sign up free and play on nlh.poker and use your stats as a GTO measuring stick over time.

Related Articles

Share this article

← Back to articles