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

What is Overbought?

Overbought describes price or oscillator extended above typical range — potential pause, not guaranteed top.

Formula

RSI Overbought Example: Price Action (10 days): Days 1-3: +2%, +3%, +2% (steady gains) Days 4-6: +4%, +3%, +5% (accelerating) Days 7-10: +2%, +1%, -0.5% (slowing) RSI Progression: Days 1-3: 55 → 60 → 62 (neutral) Days 4-6: 68 → 72 → 78 (overbought) Days 7-10: 75 → 71 → 68 (cooling) Interpretation: - RSI above 70 = overbought warning - Price may pause or pull back - But strong trends can stay overbought

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 Overbought shows up on Indian index, equity, and futures books — update to live quotes in your journal.

Nifty 50 perspective

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

Reliance Industries perspective

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

Bank Nifty futures perspective

Overbought 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 Overbought on paper or sim for two weeks after rule changes.
  • Validate only on trades where Overbought 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 Overbought reading to trade entry notes (value + timeframe).
  • Create tags: “Overbought aligned” / “Overbought 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 Overbought 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 Overbought parameters.
  • Skip trading when Overbought conflicts with written risk limits.

Common pitfalls

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

How to use this in TradeLyser

Log oscillator reading at entry when fading; review trend vs range weeks.

Related terms

FAQ

RSI 70 always sell?

Not in strong trends — your tag data decides.

Overbought on weekly?

Stronger mean-reversion signal for some swing rules.

Start journaling with TradeLyser

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