Mumbai FC
association football club

Mumbai Football Club was an Indian professional football club based in Mumbai, Maharashtra. The club predominantly competed in I-League, then top flight of Indian football league system. Mumbai also participated in MDFA Elite League, now known as Mumbai Premier League. The club was founded in 2007, with the objective of providing a platform for the young aspiring footballers from the city to showcase their talent and to try to make it to the big stage. They were nicknamed both "Mumbaikars," and "Yellow Brigade."
The club gained promotion to the I-League after winning the 2008 I-League 2nd Division, and finished 7th in their maiden I-League campaign in 2008–09 season. Mumbai FC has a local rivalry with another Mumbai-based club Air India and state rivalry with Pune dubbed as the 'Maha' derby as both clubs play in the state of Maharashtra. The club became defunct by 2019.
History
Beginning
Mumbai FC was officially founded at a grand launch in Mumbai on 27 June 2007. The club was created to provide Indian football another non-institutional club and to provide young aspiring footballers in the city a chance to show off their skills on a proper platform. Mumbai FC then set about their goals in which they wanted to build a strong first team, build a good youth development program which would serve as the platform in the ladder to the first-team for potential youngsters, build a good football culture in Mumbai, and develop the football infrastructure in Mumbai.
Begin with the source’s own compact description: “Mumbai FC” is association football club. The dossier treats that line as a proposition to test through Mumbai, association and football, not as a finished interpretation.
Why this record matters
The phrase “association football club” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Jul 4, 2026. The linked authority identifier is Q1339576. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2007, 2008 and 2019.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Mumbai FC”, its source revision and the description used here.
- Expand the search: follow Mumbai FC primary sources, Mumbai FC archive and Mumbai research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Mumbai FC”?
- Who created the surviving record, and for what administrative purpose?
- Which voices are present, absent or mediated by the institution?
Search terms from this dossier
This entry incorporates text from “Mumbai FC” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.