Engro Corporation
publicly listed conglomerate in Pakistan
Engro Corporation Limited, formerly Engro Chemicals Pakistan Limited, and commonly known as Engro (Urdu pronunciation: [ɛn.ˈɡɾoː] en-GROW), is a Pakistani conglomerate headquartered in Karachi. It was founded as Esso Fertilizer in 1965 by Esso. Its subsidiaries, including Engro Energy, Engro Enfrashare, Engro Elengy Terminal, Engro Eximp FZE, Engro Eximp Agriproducts, Engro Fertilizers, Engro Polymer & Chemicals, and Engro Vopak Terminal, operate in energy, petrochemicals, fertilizers, port terminals, and telecommunications towers.
History
Engro Corporation was originally incorporated as Esso Pakistan Fertilizer Company in 1965 by Esso Standard Eastern to manufacture fertilizer in Pakistan based on the gas reserves it discovered in 1957 near Daharki, Ghotki District, Sindh. Subsequently, it was listed on the Karachi Stock Exchange with the shareholding pattern of 75 percent owned by Esso (US$19 million) and 25 percent by the general public. A urea plant with a production capacity of 173,000 tons was constructed at the cost of US$42 million. The construction of plant began in 1966 and in 1968 it became operational.
In 1978, Esso's parent company was renamed as Exxon and accordingly Esso in Pakistan was renamed as Exxon Chemical Pakistan.
In 1988, Exxon increased its production capacity to 268,000 tons through debottlenecking.
In 1991, Exxon exited Pakistan and its shareholding of 75 percent was acquired by the employees of Exxon Chemical Pakistan in the management buyout.
“Engro Corporation” enters the record as publicly listed conglomerate in Pakistan. Crown Archives preserves that source wording while asking what Engro, Corporation and publicly can confirm, complicate or overturn.
Why this record matters
“Engro Corporation” is worth following because a concise public description often conceals a longer documentary argument. Here, Engro, Corporation and publicly provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jun 15, 2026. The linked authority identifier is Q5378747. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1965, 1957, 1966 and 1968.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Engro Corporation”, its source revision and the description used here.
- Expand the search: follow Engro Corporation primary sources, Engro Corporation archive and Engro 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 “Engro Corporation”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Engro Corporation” 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.