Brandtree

Guangshen Railway: brands it owns and its ownership tree

Guangshen Railway (HKEX: 00525, SSE: 601333) is a publicly listed company headquartered in Shenzhen, China that owns 1 consumer brand.[1]

Guangshen Railway Company Limited is a joint stock company set up on 6 March 1996 and headquartered in Shenzhen, with H shares listed in Hong Kong (00525) and A shares in Shanghai (601333), according to its 2025 annual report. The report says China Railway Guangzhou Group holds 37.12% and is the controlling shareholder, and that China State Railway Group is the actual controller.

Company facts

Legal name
Guangshen Railway Company Limited
Type
publicly listed company · see all publicly listed company owners
Headquarters
🇨🇳 Shenzhen, China
Tickers
HKEX: 00525 SSE: 601333
Last verified
· 1 sources

Guangshen Railway in numbers

Everything Guangshen Railway owns

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

Everything Guangshen Railway owns Tree of 1 brands under Guangshen Railway. Guangshen Railway Guangshen Railway

Full-screen interactive tree →

Brand portfolio by category

Full portfolio, 1 brands, with sources →

Recent changes to this record

All changes →

Frequently asked questions

What brands does Guangshen Railway own?

Guangshen Railway owns 1 consumer brands tracked here, including Guangshen Railway.

Is Guangshen Railway a Chinese company?

Yes. Guangshen Railway is headquartered in Shenzhen, China.

Who owns Guangshen Railway?

Guangshen Railway is a publicly listed company owned by its shareholders; it trades as 00525 on the HKEX and 601333 on the SSE.

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] Guangshen Railway Company Limited Annual Report 2025 — Guangshen Railway Company Limited (HKEXnews), Annual report, published 30 March 2026; retrieved 5 October 2026.

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