Historically 85% of time nifty intraday range was above 2.3%. Taking Counter trade after this number is reached is useful. Tuesday was near this number. Was expecting a fall on Wednesday. Was holding puts from tuesday closing. Reaped 1.1 lac at open sterday.
More from Niftylongterm
#Nifty watch this trendline to be taken out for a good long trade! https://t.co/nC32qh2rOO
#Nifty perfect reversal after filling the gap and testing the middle of the channel.
— Trendline Investor (@dmdsplyinvestor) June 28, 2022
Waiting for Nifty to take out that major horizontal resistance and then we can see a good short term rally. https://t.co/m3hwcWno9q pic.twitter.com/WhhLPc9JaC
Nifty 50-Until 16600 is crossed then there is every chance of one more leg downwards (Wave5)
If it closes below 15700 then we can see 15500/15160
5th wave-can get truncated,
Get rid of kachra!!
Good opportunity to accumulate quality companies
chart👇
cheers https://t.co/b0M5QRcq7e
If it closes below 15700 then we can see 15500/15160
5th wave-can get truncated,
Get rid of kachra!!
Good opportunity to accumulate quality companies
chart👇
cheers https://t.co/b0M5QRcq7e
Please use the opportunity to move out of the low-quality companies into high-quality companies.
— Moneyspinners - Work Hard, Dream Big!! (@Jai0409) May 18, 2022
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.