System Quality Number (SQN)
A good SQN is 2.5 or above over at least 100 trades. Scores of 3.0–5.0 are excellent. Anything below 2.0 on 100+ live trades signals the edge is too thin to trade with confidence.
7-day money-back guarantee
The Formula
SQN = (Expectancy / StdDev of R) × √N Where: - **Expectancy** = Mean R-multiple per trade (average profit/loss expressed as a multiple of initial risk) - **StdDev of R** = Standard deviation of all R-multiples in the sample - **N** = Number of trades in the sample - **√N** = Square root of trade count (the opportunity factor)
Benchmark Ranges
| Level | Range | What It Means |
|---|---|---|
| Holy Grail | 7.0+ | Theoretical upper bound; practically unachievable over large samples |
| Superb | 5.0 – 7.0 | Exceptional consistency and edge; rare in live trading |
| Excellent | 3.0 – 5.0 | Strong, reliable system worth scaling |
| Good | 2.5 – 2.9 | Solid edge with acceptable variance |
| Average | 2.0 – 2.4 | Marginal edge; survives but offers little room for error |
| Below Average | 1.6 – 1.9 | Insufficient edge; likely to fail under real drawdown pressure |
| Poor | Below 1.6 | No reliable edge detected; do not trade live |
How to Track
Express every trade result as an R-multiple: divide net P&L by the initial dollar risk (1R)
Accumulate at least 30 trades before calculating SQN; target 100+ for a reliable reading
Calculate mean and standard deviation of all R-multiples in the sample
Apply the formula: (mean R / StdDev R) × √N
Recalculate SQN as new trades are added, tracking how the score stabilizes over time
How to Improve
Tighten stop placement to reduce outsized losing R-multiples that inflate StdDev
Filter out low-conviction setups to raise mean expectancy without adding erratic trades
Increase trade frequency on proven setups — more trades reduce statistical noise and reward a real edge
Review trades with R-multiples below -2R; recurring outliers destroy SQN more than any other factor
Normalize position sizing to 1R before calculating — inconsistent risk sizing corrupts the R-multiple distribution
System Quality Number (SQN), developed by Van Tharp and published in Trade Your Way to Financial Freedom (2nd ed., 2006), answers a question no single metric can: is this trading system genuinely good, or was the outcome luck? By combining average expectancy, the consistency of results, and the size of the trade sample into one score, SQN gives systematic traders a statistically grounded benchmark for evaluating their edge — and knowing when the evidence is too thin to trust.
Formula & Calculation
SQN = (Expectancy / StdDev of R) × √N
Where:
- Expectancy = Mean R-multiple per trade (average P&L divided by initial risk per trade)
- StdDev of R = Standard deviation of all R-multiples in the sample
- N = Number of trades
- √N = Square root of trade count
The ratio (Expectancy / StdDev of R) is essentially a signal-to-noise ratio for the system — how large the average gain is relative to the volatility of outcomes. Multiplying by √N rewards systems that have produced that signal consistently across many trades. A high expectancy means little if results are chaotic; SQN penalizes that chaos through the StdDev denominator.
To calculate R-multiples: divide each trade’s net P&L by the initial dollar risk on that trade. If a trade risked $400 and returned $600, the R-multiple is +1.5R. If it lost $200, it is -0.5R. Collect these across all trades, compute the mean and standard deviation, then apply the formula.
Benchmarks
Van Tharp’s published rating scale (from Trade Your Way to Financial Freedom, 2006):
| Level | Range | What It Means |
|---|---|---|
| Holy Grail | 7.0+ | Theoretical upper bound; practically unachievable at scale |
| Superb | 5.0 – 7.0 | Exceptional consistency and edge; rare in live trading |
| Excellent | 3.0 – 5.0 | Strong, reliable system worth scaling |
| Good | 2.5 – 2.9 | Solid edge with acceptable variance |
| Average | 2.0 – 2.4 | Marginal edge; little room for execution error |
| Below Average | 1.6 – 1.9 | Insufficient edge; likely fails under real drawdown |
| Poor | Below 1.6 | No reliable edge detected |
These ratings assume a statistically meaningful sample (100+ trades). Apply them to small samples at your peril.
Practical Example
A futures trader runs 100 ES mini trades over 6 months, risking exactly 1R = $500 per trade (2 ES points × $250/point). After logging all trades:
- Mean R-multiple per trade: +0.35R
- Standard deviation of R-multiples: 1.05R
SQN = (0.35 / 1.05) × √100 = 0.333 × 10 = 3.33
This places the system in the Excellent tier — a meaningful result after 100 trades.
Now consider the same system evaluated after only 25 trades with identical stats:
SQN = (0.35 / 1.05) × √25 = 0.333 × 5 = 1.67
That reads as Below Average — a score that would lead most traders to abandon a viable strategy. The edge is identical; only the sample size changed. This is the sample size trap: at N=30, √N ≈ 5.5; at N=100, √N = 10; at N=400, √N = 20. A system needs enough trades to let the multiplier reflect genuine evidence, not just inflate a small lucky streak.
How to Track SQN
- Record every trade as an R-multiple — divide net P&L by the initial dollar risk on that trade before position sizing is applied.
- Accumulate at least 30 trades before calculating; target 100+ for any system evaluation that will influence live capital decisions.
- Calculate mean and standard deviation of the full R-multiple distribution using a spreadsheet or journal software.
- Apply the formula — (mean R / StdDev R) × √N — and note the N alongside the score every time you report it.
- Track SQN over time as new trades are added; a stabilizing score is itself a signal that the sample is approaching statistical validity.
How to Improve SQN
- Reduce outlier losses — trades that close at -3R or worse inflate StdDev disproportionately. Moving stops to breakeven after 1R of favorable movement caps the left tail without sacrificing upside.
- Filter low-conviction setups — removing trades that don’t meet all entry criteria raises mean expectancy; even one fewer bad trade per 20 meaningfully shifts the ratio.
- Increase frequency on proven setups — if the expectancy and StdDev are already favorable, more trades directly improve SQN through the √N factor. Scan more instruments or lower the timeframe if the setup quality holds.
- Normalize position sizing to 1R before calculating — if your risk per trade varies widely, R-multiples become distorted and StdDev rises artificially.
- Audit recurring -2R+ losses — these outliers are usually execution failures (late entries, missed stops) rather than system failures. Fixing execution improves SQN faster than changing entry logic.
Common Mistakes
- Evaluating SQN on fewer than 30 trades — the √N multiplier makes a 20-trade SQN of 4.0 nearly meaningless. Always show N alongside any SQN figure you report or act on.
- Using dollar P&L instead of R-multiples — dollar-based SQN is distorted by inconsistent position sizing and cannot be compared across instruments or time periods when risk varied.
- Abandoning a system after a low reading on small N — the example above (3.33 at N=100, 1.67 at N=25) is not hypothetical. Many traders quit systems that would have validated at 100 trades.
- Ignoring the StdDev component — a system with 0.8R mean expectancy but StdDev of 3.0R scores lower than one with 0.4R mean and StdDev of 0.8R. Consistency matters as much as magnitude.
- Comparing SQN scores from different sample sizes — an SQN of 3.5 at N=50 and 3.5 at N=200 are not equivalent signals of edge quality. The larger sample is substantially more meaningful.
How JournalPlus Calculates SQN
JournalPlus calculates SQN automatically from your trade log, converting each closed trade into an R-multiple using the initial stop distance you logged at entry. The analytics dashboard displays your current SQN score alongside the trade count used in the calculation, so you always see N in context. As you add trades, the score updates in real time, and the performance charts let you track SQN over rolling windows (30, 50, 100 trades) to see how it stabilizes. You can filter by setup type, instrument, or date range to calculate SQN for a specific strategy subset — useful for comparing two setups running simultaneously without mixing their distributions.
For deeper analysis, export your R-multiple distribution to CSV and inspect the full histogram of outcomes, which reveals whether a mediocre SQN is driven by a few outlier losses or a persistently low expectancy — two problems that require very different fixes.
Internal links: Expectancy · Profit Factor · Win Rate · Risk-Reward Ratio · Sharpe Ratio
Common Mistakes
Evaluating SQN on fewer than 30 trades — the √N multiplier inflates scores on small samples, making a marginal system look excellent
Using dollar P&L instead of R-multiples — this makes SQN sensitive to position sizing changes rather than actual edge
Abandoning a system after a low SQN reading on 20–30 trades without waiting for statistical validity at 100 trades
Ignoring StdDev — a high-expectancy system with wild variance can score lower than a low-expectancy system with tight, consistent results
Comparing SQN scores from different sample sizes as if they are equivalent — always note N alongside the score
Frequently Asked Questions
What is a good SQN score?
Van Tharp's scale rates 2.5–2.9 as good, 3.0–5.0 as excellent, and 5.0–7.0 as superb. For live trading over 100+ trades, a score above 2.5 is a credible signal of a working edge. Below 2.0 over 100 trades is a warning to pause and audit.
How many trades do I need to calculate a reliable SQN?
A minimum of 30 trades gives a preliminary reading, but the Van Tharp Institute recommends 100+ trades for live-system evaluation. Below 30, the √N multiplier inflates the score enough to make a poor system look good.
How is SQN different from the Sharpe ratio?
The Sharpe ratio uses dollar P&L, making it sensitive to position sizing and not comparable across instruments. SQN uses R-multiples (profit/loss as a fraction of risk), which are broker-agnostic and force precise risk definition before evaluating performance.
Can SQN be used for discretionary trading?
Yes, but only if every trade has a clearly defined initial stop (1R). Without consistent risk definition, R-multiples are meaningless and SQN becomes noise. Systematic traders benefit most because their 1R is always explicit.
Why does SQN rise naturally with more trades?
The √N component directly scales with sample size. A system with 400 trades and the same expectancy and StdDev as one with 100 trades will show twice the SQN score (√400 = 20 vs √100 = 10). This is intentional — more evidence of edge deserves a higher score — but it means you must never compare SQN scores across different N values without context.
What does a negative SQN mean?
A negative SQN means the mean R-multiple (expectancy) is negative — the system loses money on average per trade. No further analysis is needed; a negative expectancy system has no edge by definition.
Should I stop trading if my SQN drops below 2.0?
On 100+ live trades, a score below 2.0 is a strong signal to pause. The edge may be too thin to survive normal drawdown cycles. Audit your trade log for setup drift, execution errors, or market regime changes before resuming.
Track Your Metrics With JournalPlus
Automatically calculate and track all your trading metrics in one place. See what's working and what's not.
Buy Now - ₹6,599 for Lifetime Buy Now - $159 for Lifetime7-day money-back guarantee