R-Multiples Explained: How to Measure Every Day Trade in R

Open any guide on this blog and the numbers come back in the same unit: a setup that returns +0.4R per trade, a loss capped at 1R, a win worth 2.5R. R is the unit nearly every serious trading metric is built on — win rate, profit factor, and expectancy all assume it. Yet most day traders have never defined their own R, so the stats they track measure nothing consistent.

Here is why that matters. The demo month below shows 8 green days out of 13 — a 62% day win rate. Counting green days, the month looks fine. Measured in R, it is down 5.80R: a few large red days cost far more units of risk than the many small green days earned. This article defines the R-multiple, shows how to calculate it on a single trade, and explains why it beats raw P&L for reviewing your own history. The examples assume US stock and ETF day trading.

Demo data in the SpiceLog calendar view, $200 = 1R. Most days are green, yet the month is −5.80R — three red days alone cost 7.8R.

What an R-multiple actually is

Your R is your initial risk on a trade — the dollars you stand to lose if the trade hits your stop, fixed at the moment you enter. For a long, that is (entry price − stop price) × shares. You define it once, at entry, and it never moves.

An R-multiple is the trade's result divided by that initial risk:

R-multiple = trade profit or loss ÷ initial risk (1R)

A trade that makes twice what you risked is +2R. One stopped out for exactly your planned risk is −1R. The framework comes from trading psychologist Van K. Tharp, who popularized R-multiples and expectancy in Trade Your Way to Financial Freedom. Its power is that it strips dollars out: every trade, large or small, is measured against the one thing you controlled going in — how much you put at risk.

How to calculate R on a single trade

Start with a winner. You buy 200 shares of NVDA at $184.00, with a stop at $182.50.

• Initial risk (1R) = ($184.00 − $182.50) × 200 = $300
• You exit at $187.00. Profit = ($187.00 − $184.00) × 200 = $600
• R-multiple = $600 ÷ $300 = +2.0R

The same NVDA trade as a demo trade detail in SpiceLog: initial risk of $300 logged at entry, +$600 result, +2.00R.

Now a loser on the same risk. You short 100 shares of MSTR at $320.00, stop at $323.00.

• Initial risk (1R) = ($323.00 − $320.00) × 100 = $300
• You cover at $323.00, stopped out. Loss = −$300
• R-multiple = −$300 ÷ $300 = −1.0R

Both trades risked $300, so both are measured against the same 1R. The winner returned two units of risk; the loser cost one. Notice the discipline this enforces: 1R is set at entry from your actual stop, not guessed afterward. If you never logged a stop, you have no R — and that is the most common reason a journal's R column is garbage.

Why R beats raw dollars

Dollars lie when your position size changes; R does not.

Say you risk $100 on a scalp and $1,000 on a swing. In dollars, a $400 scalp win and a $400 swing win look identical — but one returned 4R and the other 0.4R. The scalp was ten times the better trade per unit of risk, and the dollar column hides that completely.

R fixes three things at once:

1. Comparing setups fairly. A $50-risk opening-range breakout and a $500-risk reversal sit on the same scale, so you can see which setup actually pays per unit of risk.
2. Surviving account growth. As your size grows, dollar figures balloon and old trades stop being comparable. A +2R trade from a $5,000 account and a +2R trade from a $50,000 account are the same quality.
3. Separating edge from sizing. A profitable dollar month can hide a negative-R process you got away with by sizing up on luck. R shows the process; dollars show the luck.

Here is that third point in a full month. In dollars it is a winning month; in R it is a losing one.

Demo data. The big dollar wins (Feb 2, 6, 12) came on days sized up to $500 per R, so each returned under 2R. The losses came at $100 per R and cost 1.9–3.1R apiece. The dollar column says the month worked; the R column says the process lost 5.9 units of risk, and only bigger size on the right days hid it.

From single trades to expectancy in R

Average your R-multiples across a batch of trades and you get expectancy in R — the average you win or lose per trade, per unit risked:

Expectancy (R) = (win rate × avg win in R) − (loss rate × avg loss in R)

Take 100 trades: 40% win at +2R, 60% lose at −1R.

• Expectancy = (0.40 × 2) − (0.60 × 1) = +0.2R per trade

That reads as: for every dollar risked, this process returns 20 cents on average — profitable despite losing 60% of the time. This is the same engine behind the other metrics on this blog: win rate tells you how often you win, profit factor tells you the overall shape, and expectancy in R tells you what one more trade is worth. Read them together, not alone.

Mistakes that corrupt your R numbers

Five things quietly break an R column:

1. Moving the stop after entry. 1R is the risk you took at entry. If you widen the stop mid-trade and a −1R becomes a −2.5R, log it against the original 1R — the extra loss is the mistake, and hiding it defeats the point.
2. No logged stop at all. A "mental stop" you never recorded leaves the trade with no 1R, so its R-multiple is a guess. If you want an R column, you need a written stop on every entry.
3. Inconsistent risk definition. Some trades measured from the hard stop, others from a "where I'd probably bail" level. Pick one rule and apply it to every trade, or the numbers aren't comparable.
4. Costs counted unevenly. Commissions, fees, and slippage belong inside every trade's result, not subtracted at month-end. Leave them out and your R runs flattering.
5. Partial fills collapsed wrong. A single scaled-in position in DAS Trader Pro can fire a dozen partial executions. If your journal averages them incorrectly, your entry price — and therefore your 1R — is wrong before you start.

How to track R from your own fills

Disclosure: SpiceLog is our product, so weigh the rest of this section with that in mind.

Doing this by hand is where most R columns die — reconciling partial fills, holding a consistent stop rule across hundreds of trades, and recomputing expectancy every week. SpiceLog is a trading journal and analytics tool for US stock and ETF day traders, built with particular depth for DAS Trader Pro. It reconciles scaled-in partial executions into one position with the correct average entry, takes the initial risk you logged, and computes R-multiples, expectancy, profit factor, and drawdown from your actual fills — without a spreadsheet in the middle.

The point isn't the tool. It's that R is only as good as the data under it: clean fills, a consistent 1R, and costs counted in. Get those right, by hand or otherwise, and the R column finally measures something you can trade on.

FAQ

What is a good R expectancy? Any positive number is an edge on paper, but it has to survive costs and a real sample. A process around +0.2R to +0.3R per trade, held over hundreds of trades, is a solid day-trading result; the exact bar depends on your trade frequency.

Can an R-multiple be negative? Yes. A trade stopped out at your planned risk is −1R; one that blows past the stop is worse. Expectancy itself can also be negative, which means the process loses money on average no matter how good a few winners felt.

How many trades before my R stats are trustworthy? More than feels comfortable. A few dozen per setup is a bare minimum for a first read, since one outlier can swing a small sample. Treat early numbers as provisional and recalculate as the sample grows.

Is an R-multiple the same as risk-reward ratio? Related but not identical. Risk-reward is a plan set before the trade (targeting 2R for 1R of risk). The R-multiple is the realized outcome after it closes. The gap between the two — planned versus actual R — is one of the most useful things a journal can show you.