TradingView Pyramiding vs Position Risk for NQ and MNQ

Adding a second or third entry changes the risk of an NQ or MNQ position, even when the original stop stays exactly where it was. A TradingView strategy can show several small entries that together create a much larger loss at that stop. Reviewing each entry in isolation misses the decision that matters: how much exposure the whole position carries after the next addition.

This guide explains TradingView pyramiding, then works through a hypothetical MNQ position one fill at a time. All prices and budgets below are teaching examples, not trade recommendations or evidence of a profitable strategy.

What TradingView pyramiding controls

In Pine Script, the pyramiding setting governs how many open trades from strategy.entry() can contribute to one position. The current documentation gives a default of 1, allowing an initial entry but no same-direction additions through that command. A value of 3 generally permits three entries in total, including the first. The setting can be changed in the strategy’s Properties. See TradingView’s declaration documentation.

Three entries could contain one contract each, or different quantities. The entry count alone therefore cannot tell you the number of contracts, the distance to a stop, or the dollars at risk. Write those limits separately before testing any scale-in rule.

Here, scaling in means adding exposure in the same direction. Adding after a favorable move and adding after an adverse move deserve separate tests: they change the distribution of entry prices and the circumstances in which maximum size is reached.

How this differs from a reversal

A reversal closes exposure in one direction and establishes exposure in the other. By default, an opposite-direction strategy.entry() order includes the quantity needed to close the existing position. A same-direction addition simply expands the position. TradingView explains this in its strategy documentation. For a separate worked example, read reversal order size versus position size.

Convert every entry into dollar exposure

CME specifies a multiplier of $20 per index point for NQ and $2 per index point for MNQ. Both contracts have a minimum price increment of 0.25 points, making one tick worth $5 for NQ and $0.50 for MNQ.

For a long entry with a stop below its fill, planned price loss equals the entry price minus the assumed stop fill, multiplied by contracts and dollar value per point. Calculate each leg, then add the results. For a short entry with a stop above its fill, reverse the price subtraction.

The calculation estimates a specified exit scenario. It cannot guarantee the fill or cap the eventual loss. Keep fees and adverse execution allowances visible rather than presenting the price-distance result as an all-in risk limit.

A three-entry MNQ example

Assume three long additions fill as intended, with a shared stop at 19,975:

• Entry A: 2 MNQ at 20,000. Planned loss is 25 points × 2 contracts × $2 = $100.

• Entry B: 1 MNQ at 20,010. Planned loss is 35 points × 1 contract × $2 = $70.

• Entry C: 1 MNQ at 20,020. Planned loss is 45 points × 1 contract × $2 = $90.

After A, planned price loss is $100. After B, it is $170. After C, it is $260 across four contracts. The third entry contributes $90, although it contains only half as many contracts as the first entry.

The quantity-weighted average entry is 20,007.50: multiply each entry price by its quantity, add those amounts, and divide by four. The cross-check is 32.50 points from that average to the stop × 4 contracts × $2 = $260.

If the same quantities and price distances were used with NQ, the planned price loss would be $2,600. Changing the symbol without resizing the position changes the dollar consequences by a factor of ten.

A tighter stop changes two different risk measurements

Suppose price is now 20,025 and the shared stop is raised to 20,005 after all four MNQ contracts are filled. At an assumed exit exactly at that stop, A would earn $20, B would lose $10, and C would lose $30. Combined price P&L would be a $20 loss before costs.

Yet the position currently has $140 of unrealized price profit: 17.50 points above the weighted average × 4 × $2. Falling from 20,025 to 20,005 would give back $160. Both figures are correct, but they answer different questions:

• Entry-to-stop result: What would this campaign earn or lose relative to its entry prices?

• Current-price-to-stop giveback: How much would current marked-to-market equity decline before that assumed exit?

A review that records only the $20 planned loss conceals the $160 decline from current equity. Choose the measurement that matches the account constraint being evaluated, and label it explicitly. If a rule depends on an equity high-water mark, examine that rule’s actual calculation rather than substituting either number automatically.

With different stops for different legs, retain a leg-by-leg ledger. A single average entry and one displayed stop cannot describe every possible exit sequence. Include realized P&L if part of the campaign has already closed.

Check the proposed addition before placing it

Consider an illustrative $240 campaign budget that includes a $30 reserve for the specified execution and fee assumptions. The price-loss allowance is therefore $210. After A and B, the example already uses $170, leaving $40.

At the proposed 20,020 entry and unchanged 19,975 stop, each additional MNQ requires $90 of price-loss allowance. The largest whole-contract addition within the remaining $40 is zero. A setting that allows another entry does not change that arithmetic.

This is a sizing decision to make before the addition. Moving a stop merely to make an oversized order fit a budget changes the exit rule and requires its own justification and testing. Also account for still-working entry orders: an unfilled order can become exposure before the next review.

Two Pine Script caveats to audit

TradingView documents two important exceptions: strategy.order() is unaffected by the pyramiding property, and multiple price-based strategy.entry() orders created on the same tick can all fill when triggered, exceeding the pyramiding limit. Inspect pending orders as well as filled trades. These behaviors are described in the official strategy reference.

Exit coverage needs a separate check. A strategy.exit() call with from_entry targets matching entry IDs; a mismatched ID creates no exit orders for those trades. Confirm that every added leg has the intended protection, including entries created after an earlier exit call. Consult TradingView’s multiple-entry exit examples.

For an audit, record a snapshot immediately after each addition: leg ID, fill, quantity, intended stop, covered quantity, pending additions, total contracts, and aggregate scenario loss. Compare the snapshot with the actual trade sequence. This makes an uncovered leg or unexpected extra fill easier to identify than scanning the equity curve.

Compare scaling rules on a consistent basis

A useful test separates the effect of entry timing from the effect of simply trading more contracts. Compare a single-entry baseline and a scale-in version under the same campaign budget, while keeping the market, test period, exit logic, and cost assumptions documented.

TradingView provides commission, slippage, and calculation settings that affect simulations; historical intrabar detail can also affect the sequence of fills. Record those choices using the strategy properties documentation. An apparent improvement that depends on a particular fill sequence deserves closer inspection.

1. Measure the largest total position and the largest planned loss after an addition.

2. Review campaigns that reached full size immediately before a losing exit.

3. Separate initial-entry results from the incremental contribution of later entries.

4. Check current-equity giveback alongside the final closed result.

5. Repeat the comparison on data that did not determine the scaling rules.

The central check is straightforward: before allowing another entry, recalculate the whole position at its intended exits. Pyramiding specifies entry behavior. A usable risk plan also needs contract quantities, price distances, exit coverage, pending-order exposure, and realistic execution assumptions.

Educational information only. Futures involve leverage and substantial risk. Hypothetical calculations and backtests do not establish future results, and stop orders do not guarantee the assumed exit price.