What this dataset is
Daily NAVs for every Indian mutual fund scheme in AMFI's public records: all scheme types (open-ended, closed-ended, interval), April 2006 onward, including matured schemes. Source: AMFI official files (daily NAVAll.txt plus the historical NAV archives). Updated 3x daily.
Coverage
| Item | Value |
|---|---|
| NAV rows | 37 million and growing daily |
| Schemes | 38,000+ (about 8,600 active, the rest matured or merged) |
| Date span | 2006-04-01 to present |
| Scheme types | Open Ended, Close Ended, Interval |
| AMCs | 71, including defunct houses (ABN AMRO, Fortis, Standard Chartered, Benchmark) |
| Update cadence | 3x daily from AMFI, with a 7-day self-healing lookback across all scheme types |
Table: nav_master
NAV history (one row per scheme per day)
| Field | Type | Description |
|---|---|---|
scheme_code | INTEGER | AMFI's numeric scheme identifier (4-7 digits). Stable for the life of a scheme plan+option. Join key to scheme_meta. |
date | DATE | NAV declaration date (YYYY-MM-DD). |
nav | DECIMAL(18,4) | Net Asset Value per unit in rupees, as published by AMFI. |
scheme_name | VARCHAR | Scheme name as it appeared in AMFI's file on that date. Names can change over a scheme's life; use the scheme master's scheme_name for the current canonical name. |
isin | VARCHAR | ISIN (Div Payout / Growth variant) as published on that date. Can be blank for older rows. For lookups use the scheme master's isin; the NAV API resolves any of a scheme's ISINs, including the reinvestment ISIN and prior ISINs. |
Table: scheme_master
Table: scheme_master
| Field | Type | Description |
|---|---|---|
scheme_code | INTEGER | AMFI scheme code. Primary key. |
scheme_name | VARCHAR | Current scheme name, following the latest AMFI filing. Fund houses are renaming schemes to match the SEBI Feb-2026 true-to-label rule, and this field updates with each filing; nav_master.scheme_name keeps the name as it appeared on each date. |
amc | VARCHAR | Asset Management Company name, as listed by AMFI. 70+ AMCs including defunct houses. |
scheme_type | VARCHAR | One of exactly three values: 'Open Ended Schemes', 'Close Ended Schemes', 'Interval Fund Schemes'. From the AMFI header prefix. |
category | VARCHAR | Full raw category text from the AMFI header (audit field). Modern: 'Equity Scheme - Large Cap Fund'. Old-style: single words like 'Income'. Prefer the clean fields below. |
category_group | VARCHAR | Raw group text before mapping (audit field). 20+ distinct values and growing: AMFI is re-filing schemes under new group headers through the SEBI Feb-2026 recategorization, so old and new group names coexist. For analysis use category_group_clean. |
category_sub | VARCHAR | SEBI sub-category (e.g. 'Large Cap Fund', 'Liquid Fund'). 50+ distinct values: old 2017 names and new SEBI Feb-2026 names (e.g. 'Short Duration Fund' and 'Short Term Fund') coexist while fund houses re-file, stored as-filed. BLANK for ambiguous old-style schemes by design; those rows will not appear in sub-category filters. |
category_group_clean | VARCHAR | RECOMMENDED category field. Exactly 4 values: Equity Scheme, Debt Scheme, Hybrid Scheme, Other Scheme. Every raw group name, old or new, maps in deterministically (Income -> Debt, Growth -> Equity, Balanced -> Hybrid, the new Income/Debt Oriented Schemes -> Debt, etc.). Solution Oriented (discontinued by SEBI in Feb 2026) and Fund of Funds sit under Other Scheme; their schemes stay fully findable via category_group and category_sub. |
isin | VARCHAR | ISIN of the Div Payout / Growth variant. 1:1 with scheme_code where present; can be blank for old matured schemes. All of a scheme's ISINs resolve on the NAV API: this one, the reinvestment ISIN (isin2), and prior ISINs of schemes whose ISIN changed - each returns the same full NAV series. |
isin2 | VARCHAR | Div Reinvestment ISIN, present only where the IDCW plan has a distinct reinvestment unit class (about 6,400 schemes). AMFI files it as a second ISIN column and writes '-' when absent. Same scheme_code and same NAV series as isin - payout and reinvestment are sub-options of the same IDCW plan, not a different fund. Blank for most schemes. |
first_date | DATE | First NAV date on record for this scheme. |
last_date | DATE | Most recent NAV date on record. For matured schemes this is their final NAV date. |
is_tracked | BOOLEAN | TRUE for the curated set of funds with additional analytics in the MFPro app. App-internal convenience flag; not included in the download file. |
is_stale | BOOLEAN | TRUE only for the ~50 schemes that have just 1-2 NAV rows in all of AMFI's records (data orphans). Everything else is FALSE, including matured schemes with real history. |
txic_code | VARCHAR | TigZig scheme identifier: a short human-readable code (AMC + type + category + keyword + plan + option, e.g. AX.O.MC.D.G displayed with dots). Deterministic and unique. See the TXIC docs section. |
scheme_plan | VARCHAR | 'Direct', 'Regular', or 'Other' (classified from the scheme name; pre-2013 schemes predate the Direct/Regular split and classify as Other). |
scheme_option | VARCHAR | 'Growth', 'IDCW', 'Bonus', or 'Other' (classified from the scheme name). AMFI names carry traps the classifier handles: 'Growth Plan - Bonus Option' is a Bonus option, a Dividend Yield fund's Growth variant is Growth, and 'Unclaimed IDCW Plan - Growth' (an unclaimed-amounts pool) is Growth. A fund can have several active variants at one scheme code each, so one fund may appear as separate Growth, IDCW and Bonus rows; the rarely-held Bonus variants carry near-zero AAUM. Count funds by name, not by code, if you need fund-level counts. |
is_active | BOOLEAN | TRUE if the scheme published a NAV within the last 45 days. Recomputed on every sync. Use this to filter live vs matured/merged schemes. |
aaum_cr | DOUBLE | Latest available quarterly Average AUM in Rupees Crore for this scheme. What AAUM is and is not (the daily-average definition, new-fund understatement, per-variant grain) is explained in full on the How the Data Is Built page, Scheme AUM section. |
aaum_quarter | VARCHAR | The AMFI quarter label the AAUM comes from, as filed, e.g. 'June-2026'. Schemes can sit on different latest quarters while AMFI publishes a new quarter progressively. |
aaum_quarter_end | DATE | The same quarter as an ISO date (June-2026 becomes 2026-06-30). Sort and filter on this and display the label; the label alone sorts alphabetically and puts March after June. |
nav_date | DATE | Date of the scheme's latest NAV. For matured schemes this is their final NAV date. |
nav | DECIMAL(18,4) | The scheme's latest NAV. For matured schemes this is the final NAV, frozen; check nav_date before treating it as current. In the parquet download nav is a DECIMAL type. |
Caveats and known quirks
The honest edges of this dataset. Read these before you draw conclusions from a gap or an outlier.
- Old-style schemes (pre-SEBI-2018 categories like Income or Growth) have a blank category_sub by design; AMFI never assigned them a modern sub-category. Filter on category_group_clean instead.
- SEBI reissued the entire categorization framework on 26 February 2026 (new category names, a Life Cycle Funds category, Solution Oriented discontinued). Fund houses re-file through late August 2026, so raw category fields show a mix of old and new vocabulary during the transition. Scheme categories and names in scheme_meta follow the latest AMFI filing; every change is recorded in an internal changelog.
- Closed-ended schemes in the early era (roughly pre-2010) often published NAVs weekly, not daily. Gaps of about 7 days in those series reflect the source cadence of that era, not missing data.
- Where AMFI's daily file and its historical archive disagreed on a NAV (9 records out of about 27,900 overlapping), the daily file's value was kept. Two of the nine were maturity-day par resets in the archive feed for dividend-payout FMPs; the daily file carried the real accrued NAV.
- NAV values are stored to 4 decimal places, matching AMFI's published precision.
- A small set of 50 schemes carries only 1-2 NAV rows in AMFI's records (flagged is_stale = true). They are kept for completeness.
How to access this data
- API: https://api.tigzig.com/mf/v1/ (self-describing catalog; single and bulk NAV, search, downloads)
- API reference: https://www.tigzig.com/apis/mf-nav
- Bulk downloads: Full NAV dataset in csv.gz, tsv.gz, parquet and sqlite, plus the scheme_master latest snapshot (format=latest, ~1 MB compressed), via the Data & API tab or GET /mf/v1/download
- For AI agents: https://www.tigzig.com/ai/apis/mf-nav.md