Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-seo-pack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/portfol1/public_html/wp/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the feedzy-rss-feeds domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/portfol1/public_html/wp/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the restrict-user-access domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/portfol1/public_html/wp/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/portfol1/public_html/wp/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the hueman domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/portfol1/public_html/wp/wp-includes/functions.php on line 6114

Deprecated: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated in /home1/portfol1/public_html/wp/wp-content/plugins/add-meta-tags/metadata/amt_basic.php on line 118
Days since a 3% correction | Portfolio Yoga

Days since a 3% correction

Once again, this blog is based on a US blog which showed that Dow has had 600 days since seeing a 3% reaction. Since our markets are in itself in the middle of a good bull run, I figured out that it would be interesting to check out as to how many occasions we had seen a 3% reaction in Nifty as well as how many days had been spent from the time we had a 3% correction last time around.

Of the total of 5529 days of data I have, Nifty has seen a fall of 3% or more on 208 occasions. In other words, Nifty on an average has a 3% correction every 26.5 days. But then again, that is the average. Right now, we are 180 days from a 3% correction (last correction >3% was on 3rd September 2013) though this is not the biggest time frame we have had between such corrections. This is not even the 2nd longest but is as on date the 5th longest time between 3% or more correction.

But what interested me was not the days that we spend now but how the reactions were more often seen during the bull run of 2003 – 2008. In fact, the highest days between a 3% or more reaction then was 155 days (in 2006). The trend seems to have changed not in 2009 when markets shot up substantially but in early 2010. Would be interesting if this indeed is a change in terms of markets not seeing a substantial correction for more days than what has been the trend earlier.

Image   

You may also like...

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.