BIZTRAC BETA
Civil engineering activities

CM PROSJEKT AS

Org. no. 971584912 Limited company (AS) Bærum Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 497,000
Incorporated 1994
Share capital NOK 150,000

CM PROSJEKT AS is registered as a limited company in Bærum, Akershus with organisation number 971584912. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1994. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Prosjekt- og byggeadministrasjon, prosjekt- og eiendomsutvikling, konsulentvirksomhet, samt enhver virksomhet som er forbundet med dette. Selskapet kan ved aksjekjøp eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 497,000
Est. value
NOK 580,000

Financial health · 2024

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.6%
Good
Equity as a share of total capital

Who owns CM PROSJEKT AS?

CONSTRUCTION MANAGEMENT AS
CM PROSJEKT AS
NOK 0 rev. · NOK 0 profit

CM PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

CM PROSJEKT AS er morselskap for 2 datterselskaper:

Frequently asked questions about CM PROSJEKT AS

Who owns CM PROSJEKT AS?

CONSTRUCTION MANAGEMENT AS is the largest registered owner, with 100.0%.

What is the revenue of CM PROSJEKT AS?

CM PROSJEKT AS had revenue of NOK 0 in 2024.

Who is the general manager of CM PROSJEKT AS?

Christian Grorud is registered as general manager of CM PROSJEKT AS.

Where is CM PROSJEKT AS based?

CM PROSJEKT AS has its business address in Bekkestua.

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.