BIZTRAC BETA
Rental and operating of own or leased real estate

CP EIENDOM AS

Org. no. 998711231 Limited company (AS) Ulstein Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK −21,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−21k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

CP EIENDOM AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 998711231. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av aksjer og verdipapirer. Konsulentvirksomhet. Kjøp, salg, utvikling og utleie av fast eiendom, samt alt som hermed står i forbindelse, herunder deltagelse i andre selskap.”.

Key figures · 2025

Operating profit
NOK −22,000
Equity
NOK −21,000

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns CP EIENDOM AS?

ILM INVEST AS
CP EIENDOM AS
· NOK −22,000 profit

CP EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does CP EIENDOM AS own?

CP EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CP EIENDOM AS

Who owns CP EIENDOM AS?

ILM INVEST AS is the largest registered owner, with 34.0%.

Who is the general manager of CP EIENDOM AS?

Idar Lindor Moldskred is registered as general manager of CP EIENDOM AS.

Where is CP EIENDOM AS based?

CP EIENDOM AS has its business address in Ulsteinvik.

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.