Poker HUD reads 24 hands — the note window opens at 60

Most HUD overlays will happily paint stats on a player after 24 hands, but the note window — the popup where you'd actually write something useful — doesn't open until 60. That mismatch is baked into the default settings of more tracking tools than people realise, and it quietly shapes what gets recorded at the table. The number that matters isn't the sample size on the HUD; it's the gap between when a stat appears and when you can act on it with a note.

Where the 24 comes from

Twenty-four hands is not an arbitrary number. It's roughly the point at which a HUD can display a full ring of preflop stats without the denominators collapsing to zero. If a player has a VPIP of 25% over 24 hands, that's six hands played — enough to render a number, not enough to mean anything. The HUD doesn't care. It renders.

The overlay's job is display, and display wants data early. So the default threshold for showing stat panels sits low, often somewhere between 20 and 30 hands depending on the skin and the site's hand-history import speed. Twenty-four is a common landing point because it's a multiple that clears the minimum sample the software needs to compute a rate across the standard stat set.

The note window is a different beast. It's tied to a separate threshold, often called a "note minimum" or "auto-note trigger" in the settings, and the default is frequently 60 hands. The reasoning, when you dig through the documentation, is that notes written on tiny samples tend to be wrong and tend to stick. A note that says "calling station" based on 24 hands can follow a player for months in your database, long after the read has been invalidated by 400 more hands of entirely different behaviour.

The practical effect at the table

You're four-tabling $1/$2 on a Wednesday night. A villain shows up in your HUD with 24 hands of history — VPIP 41%, PFR 6%. That's a limper, obviously. You want to write it down. The note window won't open.

So you do what most people do: you keep the read in your head, or you write it in a text file, or you just remember it. And then you forget it, because you're four-tabling and the session runs to 2am and the next time this player appears you've got 60 hands on them and the note window opens and you write "loose passive preflop" — which is true, but it's the same note you'd have written 36 hands earlier.

The 24-versus-60 gap isn't a bug. It's a deliberate friction, and it's worth understanding why it exists before you decide whether to override it.

Why 60 is the default, and whether it should be

Sixty hands is the point at which preflop stats start to stabilise enough that a note has a reasonable chance of being accurate six months later. VPIP over 60 hands has a standard error of roughly 5.6 percentage points. Over 24 hands it's closer to 8.8. Neither is great, but 60 is meaningfully better, and for the specific purpose of a permanent written note, "meaningfully better" is the bar.

The counterargument is that notes aren't only about preflop tendencies. If a player open-shoves the river on a board where they can't have value, you want to note that on hand 12, not hand 60. The 60-hand threshold doesn't distinguish between "this player limps too much" and "this player has a specific exploitable line." Both get gated behind the same wall.

Most tools let you override the threshold. In PokerTracker the setting lives under the note/auto-note configuration; in Holdem Manager it's in the HUD options. Lowering it to 24 or even 1 is a two-click job. The question is whether you should.

The case for keeping 60

If you lower the threshold, you'll write more notes, and more of them will be wrong. A player who is 41/6 over 24 hands might be 22/18 over 600. The note persists. Over a year of play, a database full of early-sample notes becomes actively misleading — you're not reading the player, you're reading a snapshot of a variance spike from eight months ago.

There's also a self-discipline argument. The 60-hand gate forces you to distinguish between reads worth writing down and reads worth holding in working memory. Most table reads are the latter. The ones that survive to 60 hands are the ones that were probably real.

What the gap actually costs you

The friction isn't free. If you play 20,000 hands a month across maybe 3,000 unique opponents, most of them you'll see for fewer than 60 hands total. Those players never get a note. They get HUD stats and nothing else — and HUD stats on 40 hands are exactly the kind of data that produces confident, wrong decisions.

This is the quiet problem with the 24/60 split: it creates a category of player who is "statistically visible but not noteworthy," and that category is most of your opponent pool. The HUD tells you they exist. The note system tells you they don't matter enough to record. Both are true, and neither is helpful when you're facing a 3-bet from someone with 38 hands of history.

The workaround most regs land on is a hybrid: keep the note threshold at 60 for permanent notes, but use colour-coding or a manual tag for anything under that. Colour codes don't carry the same weight as a written note — they're easier to overwrite, easier to ignore — but they let you flag a player at hand 24 without committing to a permanent record.

The settings question nobody asks

The more interesting question isn't whether to lower the note threshold. It's why the two thresholds are coupled at all. A HUD stat panel and a written note serve different purposes: the panel is a live read, the note is an archive. There's no particular reason the archive should open at the same time the live read becomes useful, and there's no particular reason it should open at 60 either — that number is a legacy default, carried over from an era when hand histories imported slower and 60 hands was a full session against one opponent.

If you're going to change one setting this month, change the note threshold — but change it deliberately, and change what you write. A note written at 24 hands should say "24-hand sample, looks loose, unconfirmed." A note written at 60 should say something you'd still believe at 600. The tool won't make that distinction for you. It just decides when the window opens.