Indicators/Market structure

Stop Clusters

Estimates where long traders' stop-losses are likely to sit below recent swing lows, then shows whether buyers defended each level after price swept it.

Stops 120 0.1 5PLTR · daily
Stops on a daily PLTR chart in StockVyze

What it measures

Traders who buy often place their stop-loss just under a recent swing low. Research on stop orders (see the references below) finds that they cluster at levels rather than spreading evenly, and that triggered stops can speed up a move. Placing them under swing lows is this indicator's assumption: a recent swing low is the obvious place for a long stop. It does not see real orders. It estimates where stops are likely to be and tracks what happens when price reaches them.

  • Every confirmed swing low adds one estimated stop. A swing low is confirmed once the three bars after it all have higher lows and none of the three bars before it went lower, so it shows up three bars after the low itself. The stop is placed stop_buffer_atr × ATR(14) below that low, with ATR measured at the swing low.
  • Each swing low counts the same. Volume does not change a stop's weight, position or ranking.
  • Stops are removed once price trades through them. Any bar whose low reaches a stop counts as a sweep of that stop.
  • Remaining stops are grouped into clusters. Nearby stops merge into one level at their average price. At most maximum_clusters of the largest non-overlapping clusters are shown.
OutputMeaning
active_markersClusters of estimated stops that price has not reached yet, drawn on the latest bar at the cluster's average price
sweep_markersThe eight most recent sweeps, drawn on the bar that swept them at the average price of the stops taken

Marker size is the number of stops in the cluster divided by the number still active, counting that total as at least five. One isolated stop draws a small marker. A cluster reaches full size only when it holds every active stop and there are at least five. For a sweep, the active total is counted just before the bar that swept them.

How to read it

Active clusters are amber. They mark levels below price where a pile of stops is likely to be waiting.

Each sweep marker changes color as the bars after it play out:

  • Amber (pending). Price has swept the level and the outcome is not decided yet.
  • Green (defended). Two consecutive closes landed at or above the swept level, and one close reached at least half an ATR above it. Sellers hit the stops, but buyers took the stock back.
  • Gray (failed). A close landed half an ATR or more below the level, or five bars passed without a defense. A bar that sweeps the level and closes that far below it fails at once. Gray does not always mean price stayed below the level: a sweep that hovers just above it without reaching the defense threshold also turns gray after five bars.

ATR in these rules is measured on the bar that swept the level. Once a sweep turns green or gray, its color stays fixed, even if price later moves the other way.

Common uses:

  • Watching for a flush. A large amber cluster just under price is where a quick drop is most likely to speed up, as stops turn into market sell orders.
  • Reading the recovery. A green sweep after a sharp dip shows the stops were taken out and the level held. Some traders look for long entries there.
  • Respecting a failed sweep. A gray sweep either closed half an ATR below the level before buyers defended it, or ran out of time after five bars. Check which happened before treating the level as support.

Tuning

  • lookback (default 120 bars) sets how far back swing lows count. A shorter lookback keeps only recent structure; a longer one keeps older lows that price has not returned to.
  • stop_buffer_atr (default 0.10) sets how far below each swing low the estimated stop sits. Raise it to model traders who leave more room.
  • maximum_clusters (default 5) caps how many active clusters are drawn.

Common mistakes

  • Treating markers as real orders. Stop orders are not public. Every marker is an estimate from price structure alone.
  • Reading active clusters as support. A cluster is where selling can speed up once price gets there, not where buyers are expected to step in.
  • Expecting it to use the bar in progress. Stop Clusters uses completed bars of the chart's timeframe. The current bar counts once it closes; on a daily chart, that is after the session settles.
  • Looking for short-side stops. It models stops below swing lows only. It does not estimate buy stops above swing highs.

Scans and alerts

Stop Clusters draws its markers on the chart. Its outputs are not available in scan or alert formulas.

Inputs

InputTypeDefaultRange
lookbackinteger12030 – 250
stop_buffer_atrnumber0.10.05 – 1
maximum_clustersinteger51 – 8

Outputs

active_markers, sweep_markers

References