Weekend Study-
Some good CANSLIM stocks that are setting well with significant compression in volatility & volume.

More from Ravi Sharma
It's a secret recipe 😋
But I can give you some pointers-
1) Choose stocks in Stage 2 with RS > 75
2) Identify these setups - Cup with Handle, High Tight Flag, Rectangle, VCP, Squat, Low Cheat, 3-C.
2) Wait for the significant contraction in daily range, volatility & Volume.
But I can give you some pointers-
1) Choose stocks in Stage 2 with RS > 75
2) Identify these setups - Cup with Handle, High Tight Flag, Rectangle, VCP, Squat, Low Cheat, 3-C.
2) Wait for the significant contraction in daily range, volatility & Volume.
How do u screen stocks???
— \u2206bhishek Jain (@AbhishekTMM) August 6, 2021
Reason and pre-analysis for #BAJAJFINSV before buy-
While buying breakouts, your odds will improve a lot when you prefer the following:
1. Strong Relative Strength.
2. Tight price range on low Volume and a pattern which is easy on eyes. https://t.co/CprKpAfgtj
While buying breakouts, your odds will improve a lot when you prefer the following:
1. Strong Relative Strength.
2. Tight price range on low Volume and a pattern which is easy on eyes. https://t.co/CprKpAfgtj

#BAJAJFINSV
— Ravi Sharma (@StocksNerd) August 14, 2021
Setting up in a tight base. Volume has been drying up.
Waiting for the breakout. pic.twitter.com/KWoGZAwkLO
I have been asked a lot about how to determine the direction of the broader market.
I have made some minor tweakings to this timing model since this tweet but it still will give you an idea and primer 👇
I have made some minor tweakings to this timing model since this tweet but it still will give you an idea and primer 👇
Trading 101 with SmallCap Index
— Ravi Sharma (@StocksNerd) August 20, 2019
1. Swing trades when bullish divergence in MACD-H forms
2. Breakout trades if Index closes above 22-Day high
3. Pullback/Pocket Pivot trades if Index consolidates constructively while13-EMA>22-EMA
4. Sell, go cash if Index breaches 10-Day low, NQA pic.twitter.com/u8VjXrU0Re
Excellent move in #TATAPOWER today.
Signs are all over the place, you just needed to read them. https://t.co/17bwpa1psj
Signs are all over the place, you just needed to read them. https://t.co/17bwpa1psj

#TATAPOWER is consolidating nicely around 50 & 10-DMA.
— Ravi Sharma (@StocksNerd) April 1, 2022
3 Pocket Pivot days in the last couple of weeks are signaling the interest of buyers.
4 months long base.
Steady growth in Earnings & Sales in the last 3 quarters.
Relative Strength: 77
Group Rank: 22 pic.twitter.com/2WFeUGiV1z
More from Screeners
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.