biztrac. BETA
COMPANY REGISTER PROFILE
927695529 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

CMS HOLDING AS

Org. no. 927695529 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 701,000
Operating profit NOK 611,000
Equity NOK 3.8m
Incorporated 2021
Share capital NOK 50,000

CMS HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 927695529. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 50,000, divided into 200 shares. The company's stated purpose is: “Kjøp og salg av aksjer & eiendom, samt medvirke i andre selskap og alt som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 701,000 in revenue and NOK 611,000 in operating profit.

Key figures · 2025

Revenue
NOK 701,000
Operating profit
NOK 611,000
▲ +305388 %
Equity
NOK 3.8m
▲ +14 %
Est. value
NOK 3.5m

Financial health · 2025

Liquidity
2.67
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
92.8%
Very good
Equity as a share of total capital

Who owns CMS HOLDING AS?

CMS HOLDING AS
NOK 701,000 rev. · NOK 611,000 profit

CMS HOLDING AS has 2 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about CMS HOLDING AS

Who owns CMS HOLDING AS?

Rajamohan Mani Sletten is the largest registered owner, with 80.0%.

What is the revenue of CMS HOLDING AS?

CMS HOLDING AS had revenue of NOK 701,000 in 2025.

Who is the general manager of CMS HOLDING AS?

Chris Mani Sletten is registered as general manager of CMS HOLDING AS.

Where is CMS HOLDING AS based?

CMS HOLDING AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.