Deprecated: Optional parameter $content declared before required parameter $post is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/functions.php on line 840

Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 553

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 594

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 534

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 543

Warning: Private methods cannot be final as they are never overridden by other classes in /home/blogcert/public_html/wp-includes/class-wp-session-tokens.php on line 69

Deprecated: Optional parameter $object_id declared before required parameter $taxonomy is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/nav-menu.php on line 1060

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 934

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 954

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 966

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 977

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 199

Deprecated: Optional parameter $block_name declared before required parameter $block_content is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/blocks.php on line 405

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 386

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 378

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 372

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 390

Warning: The magic method OCDI\OneClickDemoImport::__wakeup() must have public visibility in /home/blogcert/public_html/wp-content/plugins/one-click-demo-import/inc/OneClickDemoImport.php on line 128

Deprecated: Optional parameter $type declared before required parameter $wrapper is implicitly treated as a required parameter in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/class-fs-logger.php on line 145

Deprecated: Return type of FS_Key_Value_Storage::offsetExists($k) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 309

Deprecated: Return type of FS_Key_Value_Storage::offsetGet($k) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 317

Deprecated: Return type of FS_Key_Value_Storage::offsetSet($k, $v) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 301

Deprecated: Return type of FS_Key_Value_Storage::offsetUnset($k) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 313

Deprecated: Return type of FS_Key_Value_Storage::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 328

Deprecated: Return type of FS_Key_Value_Storage::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 339

Deprecated: Return type of FS_Key_Value_Storage::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 350

Deprecated: Return type of FS_Key_Value_Storage::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 362

Deprecated: Return type of FS_Key_Value_Storage::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 375

Deprecated: Return type of FS_Key_Value_Storage::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 389

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/blogcert/public_html/wp-includes/class-wp.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/blogcert/public_html/wp-includes/wp-db.php on line 3008

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378
{"id":1324,"date":"2019-11-26T09:43:53","date_gmt":"2019-11-26T09:43:53","guid":{"rendered":"https:\/\/blog.certifiedfinancialguardian.com\/?p=1324"},"modified":"2019-11-26T09:49:34","modified_gmt":"2019-11-26T09:49:34","slug":"did-the-latest-nfos-make-money-for-investors","status":"publish","type":"post","link":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/2019\/11\/26\/did-the-latest-nfos-make-money-for-investors\/","title":{"rendered":"Did The Latest NFOs Make Money For Investors?"},"content":{"rendered":"\n

The Indian mutual fund industry’s asset under management (AUM) is at an all-time high at Rs 23.13 lakh crore as on October 31, 2019. For 65 consecutive months the number of folios (accounts) rose to reach 8.63 crore at the end of October.<\/p>\n\n\n\n

With India’s ambitious target of transforming into a USD 5-trillion economy by 2025, the financial markets are likely to rise in tandem. Thus, investors are showing confidence in mutual fund<\/a> industry even as the equity markets have been volatile since the beginning of 2018.<\/p>\n\n\n\n

This could be the reason why various mutual fund players have been launching new schemes. Since the beginning of 2018, 192 schemes were launched (excluding Fixed Maturity Plans, Capital Protection Funds and Interval Funds), of which 105 were launched in 2018. The combined first portfolio AUM of all these schemes was Rs 20,000 crore.<\/p>\n\n\n\n

[Read:\u00a0<\/strong>Should You Invest In A Mutual Fund Scheme Looking At Its AUM?<\/a>]<\/p>\n\n\n\n

Let’s see how these funds have performed till now…
<\/p>\n\n\n\n

Table: Performance of new schemes launched since January 2018<\/em><\/strong><\/p>\n\n\n\n

\n
\n\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t
<\/td>\n\t\t\tAverage Returns (%)<\/strong><\/td>\n\t\t<\/tr>\n\t\t
Category<\/strong><\/td>\n\t\t\t1 Month<\/strong><\/td>\n\t\t\t3 Month<\/strong><\/td>\n\t\t\t6 Month<\/strong><\/td>\n\t\t\t9 Month<\/strong><\/td>\n\t\t\t1 Year<\/strong><\/td>\n\t\t<\/tr>\n\t\t
Equity<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t<\/tr>\n\t\t
Market cap Fund<\/td>\n\t\t\t5.34<\/td>\n\t\t\t9.15<\/td>\n\t\t\t5.23<\/td>\n\t\t\t10.46<\/td>\n\t\t\t8.10<\/td>\n\t\t<\/tr>\n\t\t
Value Fund<\/td>\n\t\t\t5.29<\/td>\n\t\t\t8.10<\/td>\n\t\t\t6.60<\/td>\n\t\t\t11.02<\/td>\n\t\t\t10.78<\/td>\n\t\t<\/tr>\n\t\t
Focused Fund<\/td>\n\t\t\t6.37<\/td>\n\t\t\t9.82<\/td>\n\t\t\t8.96<\/td>\n\t\t\t13.5<\/td>\n\t\t\t12.9<\/td>\n\t\t<\/tr>\n\t\t
Thematic\/Sector Fund<\/td>\n\t\t\t4.93<\/td>\n\t\t\t7.37<\/td>\n\t\t\t5.87<\/td>\n\t\t\t9.41<\/td>\n\t\t\t9.32<\/td>\n\t\t<\/tr>\n\t\t
Hybrid<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t<\/tr>\n\t\t
Aggressive Hybrid Fund<\/td>\n\t\t\t4.21<\/td>\n\t\t\t7.81<\/td>\n\t\t\t9.18<\/td>\n\t\t\t12.83<\/td>\n\t\t\t15.28<\/td>\n\t\t<\/tr>\n\t\t
Arbitrage Fund<\/td>\n\t\t\t0.40<\/td>\n\t\t\t1.41<\/td>\n\t\t\t3.22<\/td>\n\t\t\t4.95<\/td>\n\t\t\t6.39<\/td>\n\t\t<\/tr>\n\t\t
Debt<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t\t<\/td>\n\t\t<\/tr>\n\t\t
Corporate Bond Fund<\/td>\n\t\t\t13.98<\/td>\n\t\t\t10.66<\/td>\n\t\t\t10.93<\/td>\n\t\t\t10.21<\/td>\n\t\t\t10.51<\/td>\n\t\t<\/tr>\n\t\t
Liquid Fund<\/td>\n\t\t\t4.94<\/td>\n\t\t\t5.30<\/td>\n\t\t\t5.80<\/td>\n\t\t\t6.16<\/td>\n\t\t\t6.16<\/td>\n\t\t<\/tr>\n\t\t
Overnight Fund<\/td>\n\t\t\t4.84<\/td>\n\t\t\t5.06<\/td>\n\t\t\t5.41<\/td>\n\t\t\t5.72<\/td>\n\t\t\t5.93<\/td>\n\t\t<\/tr>\n\t<\/tbody>\n<\/table>\n<\/div>\n<\/center>\n\n\n\n

Returns are Absolute – Direct plans considered (for 192 schemes excluding Fixed Maturity Plans, Capital Protection Funds and Interval Funds)
Data as on November 12, 2019
(Source: ACE MF)<\/p>\n\n\n\n

Mutual fund houses launched schemes across categories during this period. Market-cap funds witnessed the highest number of launches predominantly in the small, mid, and multi-cap category. Small and mid cap stocks have been beaten down sharply due to various macro-economic factors. Thus, fund managers believe that this could be a good entry point for picking stocks with healthy long term potential.<\/p>\n\n\n\n

[Read:\u00a0<\/strong>Does It Make Sense To Continue SIP-Ping Into A Small-Cap Fund Now?<\/a>]<\/p>\n\n\n\n

Sector funds saw a good number of launches, especially in the Consumption and Healthcare segment. While the consumption sector is grappling with low demand from both rural and urban areas, the healthcare sector is facing compliance issues and pricing pressures. The new launches in these sectors could mean that the respective fund houses are hopeful of revival.<\/p>\n\n\n\n

[Read:\u00a0<\/strong>‘Consumption Funds’ — Has India Lost Its Appetite For Consumption?<\/a>]<\/p>\n\n\n\n

In the debt category, most launches were in the Overnight funds. Debt mutual fund investors have been cautious after it came to light that many funds have exposure to toxic and downgraded debt papers. Since then, debt investors have found solace in less risky and low volatility funds like Overnight funds.<\/p>\n\n\n\n

[Read:\u00a0<\/strong>Liquid Funds v\/s Overnight Funds: Where To Park Your Short-Term Money?<\/a>]<\/p>\n\n\n\n

Should you invest in NFOs?<\/p>\n\n\n\n

Although some of the recently launched schemes across categories have performed well during their short track record, ideally performance of at least three years must be assessed for equity schemes to determine its worthiness.<\/p>\n\n\n\n

When you invest in a NFO, a reliable track record of the fund’s performance, portfolio quality, risk-return profile, etc. that will help you determine if it is a worthy scheme for your portfolio is non-existent. Due to the lack of this information, you have to rely on the efficiency and track record of the fund house.<\/p>\n\n\n\n

Often, new funds are launched when the investor sentiments are high, such as during a market rally. This limits the fund manager’s chances to pick stocks at bargain price. Timing of NFO launch becomes even more crucial in case of sectoral and thematic funds.<\/p>\n\n\n\n

It is important to check the investment mandate of the product being launched. The product should be suitable for your risk appetite and investment horizon and must enable you to realise your goals.<\/p>\n\n\n\n

[Read: <\/strong>Why You Should Be Careful About Investing In NFOs<\/a>]<\/p>\n\n\n\n

SEBI has mandated that a fund house can launch only one scheme per category. However, this restriction is not applicable on close-ended schemes. Mutual funds saw this as a way to grow their AUM through NFOs in close-ended schemes.<\/p>\n\n\n\n

But here is why you should avoid close-ended schemes…<\/p>\n\n\n\n