MFPro's NAV database aims to hold every NAV that exists in AMFI's public records: all scheme types, April 2006 onward, including schemes that matured years ago. This page explains where the data comes from, how it is kept current, how it was assembled, and how we validate it.
The sources
Everything comes from AMFI's official public files. Two feeds: the daily NAVAll.txt file, which has the latest NAV for every scheme currently publishing (all types: open-ended, closed-ended, interval), and AMFI's historical NAV archives, which serve past NAVs and are organized by scheme type (the tp=1, tp=2, tp=3 parameters visible in AMFI's own download URLs).
The archives begin in April 2006. We probed earlier ranges (2004, 2005, early 2006) and they are empty at the source, so the data starts in April 2006.
How it stays current
A sync runs three times a day. It fetches the daily file plus a 7-day window from the historical archives for all three scheme types, merges them, and inserts anything new. Where both feeds have the same scheme and date, the daily file's value wins. Zero-value NAVs in these daily feeds are filtered out before insert. If AMFI publishes a correction, the corrected value replaces the old one.
If a sync is down for a few days, the 7-day lookback on the next sync picks up the missed days for every scheme type.
Every NAVAll file we fetch is also archived verbatim, compressed and timestamped, before any parsing happens. The stored files show what AMFI published on each day.
The SEBI Feb-2026 recategorization: how the transition is handled
SEBI reissued the entire mutual fund categorization framework on 26 February 2026: new category names across the debt ladder, Sectoral and Thematic split into two categories, a brand new Life Cycle Funds category, Solution Oriented schemes discontinued, and a true-to-label rule that forces fund names to match their category. Fund houses re-filed their schemes through late August 2026, and AMFI's daily files still hold a mix of old and new vocabulary.
How MFPro handles it: scheme categories and names follow the latest AMFI filing, refreshed on every sync, with every change recorded in an internal changelog for audit. Raw category fields are stored exactly as AMFI files them, old or new. The clean category field maps everything into 4 stable groups (Equity, Debt, Hybrid, Other). Renamed categories are treated as one category in analytics, so a fund stays in its peer group when only the label changed. A daily vocabulary watch flags any category name we have not seen before, the same day it first appears in AMFI's files.
Values from the transition period are kept as AMFI filed them. Example: a gold ETF briefly showed under an Equity ETF header in AMFI's file during the re-filing rush. The record changes when a later AMFI filing changes it, and the change history is kept.
Scheme AUM: the daily fund size, and the quarterly average (AAUM)
What the AUM figure is
The AUM figure in MFPro is the fund's total assets under management on a date. It covers all plans and options of the fund together, in Rupees Crore. It shows on the fund page, in Quick View and Category Analytics, in the AUM filters and in the AUM weighted charts. It comes from AMFI's daily fund performance data, which we read three times a day. The date it is from is shown beside it.
How each fund is linked
AMFI's daily data names each fund but has no scheme code. We link each fund to our schemes by its Regular and Direct NAVs on that date. Both NAVs must belong to the same fund, and names are never used to make a link. Funds that cannot be linked cleanly are listed on the Data Quality page under Anomalies, each with its reason.
Dates and marks
AMFI marks some figures as the most recent value the fund house shared. Such a figure can be a few days older than the date shown. The same figure appears on every plan of one fund.
Coverage
Most active funds are in AMFI's daily data. A fund that AMFI does not list, or whose AMFI row could not be matched, shows no AUM. The Data Quality page lists each AMFI row that could not be matched.
The quarterly average AUM (AAUM)
Each fund's Costs and size tab also shows AMFI's quarterly Average AUM, known as AAUM. This is the average of a scheme's daily net assets over every calendar day of the quarter, computed to a uniform standard set by SEBI, consolidated in SEBI's Master Circular for Mutual Funds dated 20 March 2026, so that every fund house averages the same way. AMFI publishes it scheme by scheme once a quarter, per plan and option, and we show it in Rupees Crore.
AAUM is the typical size the fund ran at during the quarter. A fund that grew through the quarter shows an AAUM below its size at quarter end, because the average includes the smaller early weeks. A scheme launched mid quarter is averaged over all calendar days of the quarter, including the days before it existed, so a new fund's first AAUM understates its real size. Each plan and option has its own AAUM, so the Direct Growth variant shows only its own share of the fund.
Coverage: MFPro carries AAUM from the December 2025 quarter onward, and a new quarter is added as AMFI publishes it. Earlier quarters, going back to the December 2010 quarter, are published on AMFI's Average AUM page if you need earlier history. As a snapshot taken on 2 October 2026: about 8,300 of the roughly 8,700 active schemes had an AAUM value and about 430 were blank, typically schemes AMFI had not yet published a figure for, including very new launches. That day about 8,100 schemes were on the June 2026 quarter and about 180 were still on December 2025. These counts change with every AMFI publication and are approximate.
The downloadable scheme master file (Data and API tab, Download Scheme Master) has these AAUM fields for every scheme, and the Data Dictionary lists each field with its type.
Scheme details on the Fund page: managers, benchmarks, riskometers and TER
The Scheme Information panel on each fund page comes from the fund's Scheme Summary Document (SSD), which fund houses file with AMFI. It shows the fund managers, the allotment (launch) date, the filed benchmarks, the riskometer, the objective, the permitted asset allocation and the fund's terms: exit load, minimum amounts, SIP terms and service providers. We check AMFI for new and updated documents once a day. Each panel shows the date the fund house last updated its document, and a document filed over a year ago is marked.
A Scheme Summary Document can list identifiers that belong to another fund. Each document is linked to a scheme only when its contents agree with that scheme. Where a fund house has filed no document, or a blank one, the panel says so.
Beside the filed values, the page shows two riskometers and a benchmark from AMFI's daily fund performance data: the fund's riskometer, its benchmark's riskometer, and the benchmark AMFI lists for the fund. These come from the same data and date as the AUM figure. Benchmark names from every source are shown in one standard form, so the same index reads the same way. The name as filed shows when you hover over it.
The TER on the fund page comes from AMFI's TER data, refreshed daily. It is matched to a scheme only by the exact SEBI scheme code in the fund's Scheme Summary Document. Where there is no exact match, no TER is shown.
These fields are shown in the app only. They are not in the download files or the public API. The Data Dictionary lists them under fund_page.
The July 2026 historical backfill
The database was originally built on the daily file alone, which only covers schemes that are alive and publishing. Two things were therefore missing: schemes that had already matured (a fixed maturity plan that ended in 2015 never appears in a 2026 daily file), and the pre-2013 history of funds still running today.
In July 2026 we downloaded AMFI's complete historical archives back to April 2006 and merged them in: about 16.4 million NAV records and roughly 20,000 schemes that existed in the past but not in the database, including funds from houses that no longer exist (ABN AMRO, Fortis, Standard Chartered, Benchmark and others).
Every download window was profiled before anything moved (row counts, date spans, blank and duplicate checks). The data was staged offline and inserted in seven separate batches, each with a before-and-after cross-tabulation by year and scheme type in which every cell had to reconcile (before + added = after) or the batch stopped. Inserts were strictly additive: where a record already existed, the existing value always won.
When an AMC merges: what happens to a fund's history
AMFI has seen dozens of AMC mergers and rebrands over the years. When an AMC's schemes move to a new owner, one of two things happens to that scheme's history. This affects since-inception analysis.
Sometimes the merging scheme is folded into an already-existing scheme of the acquiring AMC. That scheme keeps its full history with no gap. For example, ING Large Cap Equity Fund's investors were moved into Aditya Birla Sun Life Large Cap Fund in the 2014 ING merger. That fund has traded continuously since 2006, before and after.
Other times, a new scheme code is created to carry the strategy forward. There, the old code's history stops on the merger date and the new code starts its own history a few days later. Looking up only the new code will not show the pre-merger years. They exist, but under a different, now-inactive code. In that same 2014 ING merger, of the roughly 128 ING schemes still trading at the time, about 49 were relaunched this way under brand new codes.
We do not yet have a systematic map connecting every old scheme code to its successor across every AMC merger in AMFI's history. Building one is on our enhancement roadmap, with no fixed timeline yet. What we know today: at least 20 AMCs have fully merged away or shut down since 2006, covering roughly 4,900 scheme codes, plus more that changed names in place (IDFC to Bandhan, Reliance to Nippon India) with no gap at all. If a scheme you are researching has a surprisingly short history, it may be the newer half of an older, longer-running fund under a different code.
Validation discipline
Where the two AMFI feeds overlapped (about 27,900 records), we compared them value by value. They disagreed on 9 records, 0.03 percent. Seven were precision differences between AMFI's own feeds. Two were cases where the archive recorded a par value of 10 on the maturity date of a dividend-payout fixed maturity plan while the daily file had the real accrued NAV. In all 9 cases the daily file's value is kept and the difference is logged.
Scheme categories for historical schemes were re-derived through the same deterministic mapping the daily sync uses, with a manually reviewed mapping table for 12 legacy category labels that predate the modern SEBI classification.
The bulk download files are regenerated after each sync to temporary paths and swapped in atomically, so a download can never be half-written. Blank text fields in the download files are uniform NULLs in every format, CSV and Parquet alike, so a null count gives the same answer whichever format you work with.
Limitations
A date missing from AMFI's records is missing here too. No values are filled in.
Old closed-ended schemes (roughly pre-2010) often published NAVs once a week. The week-long gaps in those series come from that.
Old-style schemes carry a blank sub-category by design; AMFI never assigned them one. The clean category group field covers every scheme.
The history holds about 400,000 NAV values of exactly 0.00, across about 3,100 schemes. About 2,300 matured schemes end their series with a 0.00, which is AMFI's closing entry for the scheme. It is not a price. Other zeros are in the middle of a series, and some schemes return to positive NAVs after a run of zeros. AMFI does not state what each zero means. They come from AMFI's archive as filed. Since March 2026 the daily sync does not store new 0.00 values. Segregated portfolios are filed at 0.00 every day, so their series stop on 9 March 2026. A segregated portfolio is a separate pool a fund creates when a bond it holds is downgraded or defaults: the troubled holding moves into the segregated portfolio, and its unit holders receive money only if that holding later recovers. Return and risk calculations skip any NAV at or below zero.
About 50 schemes have only one or two NAV rows in all of AMFI's records. They are kept in the data, with is_stale set to TRUE.
The full field-by-field detail, including every caveat, lives in the Data Dictionary section.
See also
Every field referenced on this page is documented in the Data Dictionary, field by field with types and caveats. The Scheme Universe field guide explains how to read the scheme master: which category field to use, plan and option variants, active versus matured.
For programmatic access, the NAV API reference covers single and bulk NAV, search and the bulk downloads, including the scheme master snapshot (format=latest). The self-describing catalog for AI agents lives at api.tigzig.com/mf/v1/.
Questions and corrections
Questions, anomalies you have spotted, or validation requests: use the Report button in the app header. Confirmed discrepancies in the source data are listed on the Data Quality page.