Nippon Logitem: brands it owns and its ownership tree
Nippon Logitem (TSE: 9060) is a publicly listed company headquartered in Tokyo, Japan that owns 1 consumer brand.[1]
JAPAN LOGISTIC SYSTEMS CORP., known in Japanese as Nippon Logitem, is a logistics company with its head office in Ebara, Shinagawa Ward, Tokyo. Its 109th annual securities report (year to 31 March 2025) says it began in October 1944 as Osaki Unso and has no parent company. Nisshin Seifun Co. is the largest holder at 20.76%, followed by Fujizakura no Kai at 17.96% and JF Kikaku at 12.11%.
-
brands owned
-
1
categories
-
0
acquisitions recorded
-
0
divestitures recorded
Company facts
- Legal name
- JAPAN LOGISTIC SYSTEMS CORP. (also 日本ロジテム, Nippon Logitem)
- Type
- publicly listed company · see all publicly listed company owners
- Headquarters
- 🇯🇵 Tokyo, Japan
- Founded
- 1944
- Tickers
- TSE: 9060
- Website
- www.logitem.co.jp
- Last verified
- · 1 sources
Nippon Logitem in numbers
- Nippon Logitem owns 1 consumer brands tracked here across 1 top-level categories; the largest is travel & transport with 1 brands.[1]
Everything Nippon Logitem 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 Nippon Logitem own?
Nippon Logitem owns 1 consumer brands tracked here, including Nippon Logitem.
Is Nippon Logitem a Japanese company?
Yes. Nippon Logitem is headquartered in Tokyo, Japan and was founded in 1944.
Who owns Nippon Logitem?
Nippon Logitem is a publicly listed company owned by its shareholders; it trades as 9060 on the TSE.
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] Annual Securities Report, 109th fiscal year (to 31 March 2025), JAPAN LOGISTIC SYSTEMS CORP. (EDINET S100W969) — JAPAN LOGISTIC SYSTEMS CORP., Annual report, published 30 June 2025; retrieved 5 October 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.