ICT Turtle Soup Strategy: How to Trade the False Breakout Reversal

Turtle Soup is one of the oldest liquidity plays in trading, and one of the cleanest. The name comes from Linda Raschke, who built the original setup to fade the famous Turtle Traders' breakout system: when their 20-day breakout failed, she took the other side. ICT adapted the concept into his liquidity framework, and today Turtle Soup is shorthand for buying a failed breakdown or selling a failed breakout.

If you already understand liquidity sweeps, Turtle Soup will feel familiar. It is the same engine: engineered stop runs, trapped traders, and a reversal powered by their exits.

What Is the ICT Turtle Soup Setup?

The setup is a three-step sequence:

1. A reference level forms. A prior swing low (for longs) or swing high (for shorts) that has held long enough for stops to build behind it. The original rule used a 20-bar low; ICT traders use any obvious swing point, prior day low, or session extreme.
2. Price breaks the level and fails. The break triggers breakout entries and stop-losses, then momentum dies. This is the liquidity grab: smart money fills large positions against the stampede of forced orders.
3. Price closes back inside the range. The failure candle closing back through the swept level confirms the trap. Everyone who chased the breakout is now underwater, and their exits fuel the reversal.

The psychology is the whole edge. A breakout trader's stop-loss is a reversal trader's entry fuel.

Turtle Soup vs. a Real Breakout: How to Tell the Difference

The question that decides your win rate: was that break genuine or engineered? Signals that favor the Turtle Soup read:

• Speed of rejection. A genuine breakout holds beyond the level and builds acceptance (candles closing outside). A sweep rejects within one to three candles.
• No displacement in the breakout direction. Real breakouts show strong-bodied candles continuing away from the level. Sweeps show long wicks and small bodies past it.
• Higher-timeframe context. A sweep of a low inside a higher-timeframe uptrend, or at a higher-timeframe demand zone, is far more likely to be Turtle Soup than the start of a breakdown.
• Where it happens. Sweeps into obvious liquidity pools (equal lows, prior day low, Asian session low) during the London or New York kill zones carry the most weight, because that is when the engineered moves actually run.

Exact Trade Rules

Long (failed breakdown)

1. Identify a swing low with visible stops behind it: equal lows, a prior day low, or a clean 20-bar low.
2. Wait for price to trade below that low.
3. Do nothing until a candle closes back above the swept level. No close back inside, no trade.
4. Enter on the close back inside, or on the retest of the level from above for a better price.
5. Stop-loss goes below the sweep extreme (the lowest wick of the raid), not below the original swing.
6. First target is the middle of the prior range; final target is the opposite side of the range or the next liquidity pool above.

Short (failed breakout)

Mirror everything: sweep of a swing high, close back below, stop above the sweep extreme, targets into the range and the lows beyond it.

Filters that remove most losers

• Trade only sweeps of levels the market has respected for hours, not minutes.
• Demand confluence: the sweep should land in a higher-timeframe zone (order block, demand, or an inverse fair value gap forming on the snap-back).
• Skip sweeps that happen in dead hours. A raid at 3 AM New York time on a forex pair is noise more often than signal.

How Turtle Soup Relates to CRT

If you have read our Candle Range Theory guide, you will notice the overlap: CRT's sweep-and-reject of a prior candle's high or low IS a Turtle Soup sequence compressed into candle logic. Turtle Soup frames it around swing points and stop clusters; CRT frames it around the prior candle's range. The trade is the same trade: liquidity taken, move rejected, range reclaimed.

That is also why this setup automates well. Our Alpha Sweep indicator is built around exactly this sequence: it flags the liquidity sweep, requires the inversion confirmation, and prints the signal with the invalidation level attached, so you are not eyeballing wicks at 2 AM.

Common Mistakes

• Entering on the break instead of the reclaim. The sweep alone is not a signal. Half of "sweeps" keep going. The close back inside is the setup.
• Stops at the obvious place. Putting your stop right under the original swing low puts you in the same pool that just got raided. Give it the sweep extreme plus a small buffer.
• Trading every swing point. The setup pays at levels where stops demonstrably cluster: equal lows, session extremes, prior day levels. Random intraday swings produce random results.
• Ignoring the trend. Turtle Soup against a strong higher-timeframe trend is picking up coins in front of the train. The best version trades sweeps in the direction of the larger flow.

Key Takeaways

• Turtle Soup fades failed breakouts of obvious swing levels where stops cluster.
• The confirmation is the close back inside the range, never the sweep itself.
• Stop goes beyond the sweep extreme; targets are the range midpoint and opposite side.
• Best results come at session extremes and prior day levels during active kill zones.
• The same sweep-and-reclaim engine powers CRT and our Alpha Sweep signal logic.