Brandtree

Who owns Gujarat Pipavav Port?

Gujarat Pipavav Port is owned by Gujarat Pipavav Port Limited (India, NSE: GPPL).[1]

This ownership is reported in official statements but has not yet been matched to a regulatory filing.

Evidence: Gujarat Pipavav Port Limited Annual Report 2024-25 (Business Responsibility and Sustainability Report), 8 August 2025. Last checked .

Key facts

Current owner
Gujarat Pipavav Port Limited reported
Owner HQ
๐Ÿ‡ฎ๐Ÿ‡ณ India
Origin
๐Ÿ‡ฎ๐Ÿ‡ณ India
Category
Travel & transport โ€บ Parcel & freight logistics
Parent ticker
NSE: GPPL
Last verified
ยท 1 sources

About Gujarat Pipavav Port

Gujarat Pipavav Port, whose website is pipavav.com, handles cargo at Pipavav in Gujarat. The company's 2024-25 sustainability report names APM Terminals Mauritius Ltd as its holding company with 44.01 percent and says it follows the sustainability framework of APM Terminals and its parent A.P. Moller - Maersk.

Ownership timeline of Gujarat Pipavav Port

  1. Current owner Gujarat Pipavav Port [1] reported

Where Gujarat Pipavav Port sits in Gujarat Pipavav Port

Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.

Where Gujarat Pipavav Port sits in Gujarat Pipavav Port Tree of 1 brands under Gujarat Pipavav Port. Gujarat Pipavav Port Gujarat Pipavav Port

Open the full Gujarat Pipavav Port ownership tree โ†’

Other brands in parcel & freight logistics, and who owns them

The 221 brands in parcel & freight logistics on Brandtree belong to 181 owners. The largest is Radiant Logistics, with 5.

BrandOwnerOwner based in
Adcom Express Radiant Logistics ๐Ÿ‡บ๐Ÿ‡ธ United States
Forward Air Forward Air ๐Ÿ‡บ๐Ÿ‡ธ United States
ABF Freight ArcBest ๐Ÿ‡บ๐Ÿ‡ธ United States
C.H. Robinson C.H. Robinson ๐Ÿ‡บ๐Ÿ‡ธ United States
FedEx Express FedEx ๐Ÿ‡บ๐Ÿ‡ธ United States
GLS IDS ๐Ÿ‡ฌ๐Ÿ‡ง United Kingdom
InPost InPost ๐Ÿ‡ฑ๐Ÿ‡บ Luxembourg
Wilhelmsen Port Services Wilh. Wilhelmsen Holding ๐Ÿ‡ณ๐Ÿ‡ด Norway

Every brand in parcel & freight logistics and its owner โ†’

About the owner: Gujarat Pipavav Port

Gujarat Pipavav Port is a publicly listed company headquartered in India. Brandtree records 1 brand under its control, and it is listed as NSE: GPPL.

Gujarat Pipavav Port Limited operates the Pipavav port in Gujarat and is listed on the NSE (symbol GPPL, ISIN INE517F01014) and BSE. Its 2024-25 Business Responsibility and Sustainability Report lists APM Terminals Mauritius Ltd as holding company with 44.01 percent and Pipavav Railway Corporation Limited as an associate with 38.80 percent. The report refers to A.P. Moller - Maersk as its parent organisation and gives its business as cargo handling incidental to water transport.

Gujarat Pipavav Port: full profile, brands and acquisition history โ†’

๐Ÿ‡ฎ๐Ÿ‡ณ Gujarat Pipavav Port and other Indian brands

Brandtree records a controlling owner for 255 brands that began in India. 9 of them (4%) are now controlled by a company headquartered in another country; Gujarat Pipavav Port is not one of them.

All Indian brands and who owns them โ†’

Frequently asked questions

Who is the parent company of Gujarat Pipavav Port?

The parent company of Gujarat Pipavav Port is Gujarat Pipavav Port Limited, a publicly listed company headquartered in India.

Is Gujarat Pipavav Port Indian?

Yes. Gujarat Pipavav Port originated in India and its owner, Gujarat Pipavav Port Limited, is also headquartered in India.

Is Gujarat Pipavav Port still owned by Gujarat Pipavav Port Limited?

Yes. As of 5 October 2026, Gujarat Pipavav Port is still owned by Gujarat Pipavav Port Limited. The ownership record was last checked against primary sources on that date.

Sources (1) & corrections

Last verified . Every ownership fact above is backed by one of these primary documents. Numbers in brackets in the text refer to this list.

  1. [1] Gujarat Pipavav Port Limited Annual Report 2024-25 (Business Responsibility and Sustainability Report) โ€” Gujarat Pipavav Port Limited, Annual report, published 8 August 2025; retrieved 5 October 2026.

Report a correction Opens a pre-filled GitHub issue. See our corrections policy.