| 会社名 | Group | 親会社 | 子会社 | 得意先 | 仕入先 | 業務提携 | 銀行等 | 株主等 |
|---|---|---|---|---|---|---|---|---|
| テン資源株式会社 | ||||||||
|
|
||||||||
| 公立学校法人首都大学東京 | ||||||||
|
|
||||||||
|
|
||||||||
|
|
||||||||
|
|
||||||||
|
|
||||||||
|
|
Founded Comprehensive Building Services. Started elevator installation, renovation, and repair work.
Established General Service Co., Ltd. Began elevator maintenance and inspection services.
Commenced maintenance and inspection work for local governments.
Founded User Co., Ltd. in Kyobashi, Chuo-ku, Tokyo by Kuniichi Niizuma (capital 20 million yen).
Capital increased to 40 million yen.
Headquarters relocated to Yaesu, Chuo-ku, Tokyo.
Company name changed from User Co., Ltd. to Comprehensive Services Co., Ltd.
Commercial paper holders 'Quin Keeper Type I, II, III' sales started.
Headquarters relocation.
Started elevator installation, maintenance, and repair work.
Business expanded into disaster prevention with sales of 'Quint Toilet'.
Business expanded into nursing care and environmental sectors.
Renamed 'Quint Toilet' to 'Sanita Clean'.
Capital increased to 70 million yen.
Kuniichi Niizuma appointed as President.
Kuniichi Niizuma appointed as Chairman.
Capital increased to 98 million yen.
Installed 2,000 elevators.
Installed 1,600 home elevators.
Opened Fukui branch office.
Commenced home elevator maintenance and inspection in Tokyo.
Opened Tokyo branch office.
Opened Hamamatsu branch office.
Elevator maintenance inspection in Chiba Prefecture started. Moving walkway maintenance inspection started.
Fukui branch office relocated for business expansion.
New business for supporting information systems of SMEs started.
Headquarters relocated to Nihonbashi, Chuo-ku, Tokyo.
Hamamatsu branch office relocated for business expansion.
Tokyo branch office relocated for business expansion.
Our contracted company completed a new factory and warehouse.
Regarding the publicly disclosed PHP vulnerabilities (CVE-2026-109618/CVE-2026-109619), the company has completed applying patch updates to the CMS environment it provides and manages, as well as related servers. Since the issue has been addressed on the server side, users do not need to change settings or perform updates. Currently, all environments using the company's CMS are not affected by this vulnerability.