#OrientElec #Watchlist
~ Listed in 2018 and has been growing strongly
~ >75% rise in EPS in last 3 qtrs accompanied with >25% sales growth in last 2 qtrs
~ Forming a Cup with handle base for last 4 months with pivot at 335
More from weTrade Charts
More from Watchlist
Im sharing A stock Screener+Swing Strategy
Criteria
Screener to Find Swing Stocks.
1. 15% Range of Near 52 week high
2. Avg Volume > 1 lakh
3. Market Cap > 2000 Cr
4. Roe Roce > 20%
5. Eps Increasing Qtr on Qtr
6. Above 50 ema
1/
How to use This Screener
1. Basically we are screening Fundamentally strong stock
2. These are Technically Strong also as stocks are near 52 week high and above 50 ema
3. Below is the list For the screened Stocks.
4. Target should be on RR
@StocksNerd @MarketScientist
2/
When to Enter
1. When 52 week High is Broken
2. Filter Stocks Select Stock With High Relative Strength
Example : #CosmoFilms , #Mastek
3. Keep Sl Below 21 ema
4. Keep Trailing Using 21 ema
5. Enter stocks on high volume breakout
6.Look for Price Range Contraction
3.
Your Most work is done by the screener
The most important task is filtering out manually and that's where your Returns will differ
As we are screening TechnoFunda stocks these can used for momentum investing
Join telegram https://t.co/b4N4oPAto9
@AmitabhJha3 @chartians
Criteria
Screener to Find Swing Stocks.
1. 15% Range of Near 52 week high
2. Avg Volume > 1 lakh
3. Market Cap > 2000 Cr
4. Roe Roce > 20%
5. Eps Increasing Qtr on Qtr
6. Above 50 ema
1/
How to use This Screener
1. Basically we are screening Fundamentally strong stock
2. These are Technically Strong also as stocks are near 52 week high and above 50 ema
3. Below is the list For the screened Stocks.
4. Target should be on RR
@StocksNerd @MarketScientist
2/
When to Enter
1. When 52 week High is Broken
2. Filter Stocks Select Stock With High Relative Strength
Example : #CosmoFilms , #Mastek
3. Keep Sl Below 21 ema
4. Keep Trailing Using 21 ema
5. Enter stocks on high volume breakout
6.Look for Price Range Contraction
3.
Your Most work is done by the screener
The most important task is filtering out manually and that's where your Returns will differ
As we are screening TechnoFunda stocks these can used for momentum investing
Join telegram https://t.co/b4N4oPAto9
@AmitabhJha3 @chartians
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.