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
Nifty Rollover vs. Next Month Return | Portfolio Yoga

Portfolio Yoga

Building Wealth | Building Relationships

Nifty Rollover vs. Next Month Return

by ·

 

Does Nifty Rollover cost (which may include dividends as well) have any relation to the kind of returns Nifty generates in the following month. Based on that thought, did a test on Nifty current month futures vs next month. All dates used as Last Thursday of the month.

Here are the results:

Image

 

When premium was > 1.0 percent, the return in the following month was the lowest. The data is from 2000 till October 2013 and hence includes months in 2008 / 09 when we saw huge swings on either side. 

If I removed the big outliers (biggest gaining month and biggest losing month), the picture comes to show like this

Image

 

While we can see the big negative bar missing, the positive does not change much showcasing that when Nifty runs in discount, the possibility of gains outweigh losses. Of course, this would be too simple a extrapolation and not useful for trade, but a thought all the same.

 

 

 

Leave a Reply

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