Tradelyser Logo
Technical Analysis
Updated 2025-06-04·Editorial policy·Trading system

What is Oversold?

Oversold is extended below typical range on price or oscillator.

Formula

RSI Oversold Example: Price Action (10 days): Days 1-3: -2%, -3%, -2% (steady decline) Days 4-6: -4%, -5%, -3% (accelerating) Days 7-10: -1%, -0.5%, +1% (slowing) RSI Progression: Days 1-3: 45 → 40 → 38 (weakening) Days 4-6: 32 → 25 → 22 (oversold) Days 7-10: 28 → 32 → 38 (recovering) Interpretation: - RSI below 30 = oversold warning - Selling may be exhausting - But weak stocks can stay oversold

Indian market context (NSE)

Reference levels: Nifty 50 at 24,300, Reliance Industries at ₹1,300, Bank Nifty futures at 55,000 (lot size 30). Examples below show how Oversold shows up on Indian index, equity, and futures books — update to live quotes in your journal.

Nifty 50 perspective

Oversold on Nifty (24,300): on the 15-minute chart, combine with session VWAP and 9:15–10:00 liquidity — index oversold signals misfire on expiry Tuesdays without volume confirmation.

Reliance Industries perspective

Oversold on Reliance at ₹1,300: daily vs hourly settings diverge around results and ex-dividend dates; note corporate events in journal when oversold readings spike.

Bank Nifty futures perspective

Oversold on Bank Nifty futures (55,000): first-hour signals differ from post-14:30 behaviour; avoid standalone entries when banking names lead the move.

How to validate

  • Forward-test Oversold on paper or sim for two weeks after rule changes.
  • Validate only on trades where Oversold settings matched the written playbook.
  • Split results by trending vs range weeks on Nifty before trusting the signal.
  • Require higher-timeframe bias agreement if that is part of your rule.

How to track in TradeLyser

  • Add Oversold reading to trade entry notes (value + timeframe).
  • Create tags: “Oversold aligned” / “Oversold ignored”.
  • Monthly: filter trades by alignment tag and compare win rate and avg R.
  • Screenshot chart context for mentor review on disputed trades.

Best practices

  • Combine Oversold with higher-timeframe bias — not as a lone trigger.
  • Avoid curve-fitting settings on less than three months of tagged data.
  • Refresh playbook screenshots when changing Oversold parameters.
  • Skip trading when Oversold conflicts with written risk limits.

Common pitfalls

  • Treating Oversold as a guaranteed reversal signal.
  • Optimising parameters on one bullish month only.
  • Trading against higher-timeframe bias because Oversold “said so”.
  • Failing to log when you overrode Oversold discretionally.

How to use this in TradeLyser

Tag oversold entries with RSI/stoch values; separate knife catches.

Related terms

FAQ

Oversold without divergence?

Weaker for many rules — note divergence tag.

Oversold on small caps?

Liquidity risk higher — size down.

Start journaling with TradeLyser

Connect your broker, tag strategies, and review performance with AI-assisted insights.