BIZTRAC BETA
Uoppgitt

CMM KAPITAL AS

Org. no. 922232407 Limited company (AS) Lørenskog Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 2.7m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

CMM KAPITAL AS is registered as a limited company in Lørenskog, Akershus with organisation number 922232407. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å eie og drive faste eiendommer samt verdipapirer og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 2.7m
Est. value
NOK 16.5m

Financial health · 2025

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

Who owns CMM KAPITAL AS?

CHRISTIAN MOBERG MITHASSEL
CMM KAPITAL AS
NOK 0 rev. · NOK −12,000 profit

CMM KAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CMM KAPITAL AS own?

CMM KAPITAL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CMM KAPITAL AS

Who owns CMM KAPITAL AS?

CHRISTIAN MOBERG MITHASSEL is the largest registered owner, with 100.0%.

What is the revenue of CMM KAPITAL AS?

CMM KAPITAL AS had revenue of NOK 0 in 2025.

Who is the general manager of CMM KAPITAL AS?

Christian Moberg Mithassel is registered as general manager of CMM KAPITAL AS.

Where is CMM KAPITAL AS based?

CMM KAPITAL AS has its business address in Fjellhamar.

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

Report a problem

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