SMRT: brands it owns and its ownership tree
SMRT is a privately held company headquartered in Singapore, Singapore that owns 2 consumer brands.[1]
SMRT Corporation Ltd was listed on the Singapore Exchange in 2000 and delisted in 2016, according to the milestones page on its own site. A joint announcement of 29 September 2016 said Temasek held about 54% and that, if the scheme of arrangement took effect, SMRT would become a wholly-owned subsidiary of Temasek. The site presents SMRT Trains and SMRT Buses as its public transport businesses and says its corporate headquarters moved to Paya Lebar Quarter in 2019.
-
brands owned
-
1
categories
-
0
acquisitions recorded
-
0
divestitures recorded
Company facts
- Legal name
- SMRT Corporation Ltd
- Type
- privately held company · see all privately held company owners
- Headquarters
- 🇸🇬 Singapore, Singapore
- Website
- www.smrt.com.sg
- Last verified
- · 1 sources
SMRT in numbers
- SMRT owns 2 consumer brands tracked here across 1 top-level categories; the largest is travel & transport with 2 brands.[1]
Everything SMRT owns
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Full-screen interactive tree →
Brand portfolio by category
Recent changes to this record
Frequently asked questions
What brands does SMRT own?
SMRT owns 2 consumer brands tracked here, including SMRT Trains and SMRT Buses.
Is SMRT a Singaporean company?
Yes. SMRT is headquartered in Singapore, Singapore.
Who owns SMRT?
SMRT is privately held. SMRT Corporation Ltd was listed on the Singapore Exchange in 2000 and delisted in 2016, according to the milestones page on its own site.
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] SMRT scheme of arrangement approved by minority shareholders — SMRT Corporation Ltd / Temasek (via SGX), Stock exchange filing, published 29 September 2016; retrieved 5 October 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.