Define Average Win Loss clearly
Average Win Loss (often written as average win and average loss) describes the typical size of profitable versus losing trades. In practice, it is verified by first confirming what “average” and “win/loss” mean in the context you are using.
To make the concept verifiable, specify at least:
- Win definition: whether the metric uses gross profit, net profit after costs, or another adjustment.
- Loss definition: whether losses are recorded as negative values, or converted to absolute magnitudes.
- Trade unit: whether each trade counts once, how partial closes are handled, and how break-even outcomes are treated.
When you see “Average Win Loss” reported, treat it as an incomplete description until the above choices are stated.
Separate stable mechanics from variable conditions
The core mechanics are generally stable: compute an average win size from the set of winning trades and an average loss size from the set of losing trades, then compare them.
However, the reported numbers change when variable conditions change. Examples include:
- Costs and fees (spreads, commissions, financing) if the metric is net rather than gross.
- Execution and slippage if outcomes are based on actual fills versus idealized prices.
- Sample selection (time period, strategy universe, and whether filtering excludes certain trade types).
Because of this, verification should focus on whether two sources use the same definitions and inputs, not only whether they quote similar figures.
Evidence and reproducible verification steps
Use a reproducible checklist that someone else can repeat using the same trade history.
-
Collect the underlying trade list
- Use a single dataset of executed trades.
- Ensure each row includes outcome information consistent with your definitions (gross or net).
-
Label wins and losses with explicit rules
- Decide the rule for break-even trades (exclude, treat as win, or treat as separate).
- Decide how partial closes are represented: one combined outcome per original position, or separate outcomes per closure.
-
Compute the two averages using stated formulas
- Average win size = sum of win outcomes ÷ number of winning trades.
- Average loss size = sum of loss outcomes ÷ number of losing trades.
- If “loss” is reported as a positive magnitude, convert consistently (for example, take absolute values) so you do not mix sign conventions.
-
Run an independent spot-check
- Pick a small subset of 5–10 trades and recompute the averages manually.
- Confirm that the totals match the reported intermediate sums and counts.
-
Document assumptions for your calculation
- Record whether outcomes are gross or net.
- Record how partials and break-even are handled.
If a source does not reveal these assumptions, treat the “verification” as not fully possible, because multiple definitions can produce different “Average Win Loss” results.
Limitations and failure modes
A material limitation is that average win and average loss are descriptive and depend heavily on how the dataset is constructed.
At least one common failure mode:
- Mixing outcome types: combining realized outcomes with adjusted values, or combining partial-close entries with whole-position entries, can distort the average.
Other limitations that affect interpretation:
- Non-stationarity: historical relationships do not establish future results.
- Window effects: changing the date range can change the composition of wins and losses.
- Cost sensitivity: net-versus-gross changes averages, especially if costs vary over time.
Verification questions to ask next
To verify information about Average Win Loss, ask the provider or author for:
- The exact definitions of win, loss, and whether outcomes are gross or net.
- How break-even trades are treated.
- How partial closes and multiple entries are aggregated into single trade outcomes.
- The dataset scope (time window and inclusion/exclusion criteria).
If those details are missing, you can still perform verification by recomputing the metric under explicit alternative assumptions and checking whether the reported conclusion depends on those assumptions.
For a deeper comparison, see related explanations such as average win loss versus nearby performance concepts and the required data fields for assessment.