BIZTRAC BETA
Civil engineering activities

KM EIENDOMSUTVIKLING AS

Org. no. 914402263 Limited company (AS) Fredrikstad Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −37,000
Equity NOK 441,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

KM EIENDOMSUTVIKLING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 914402263. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Prosjektering av bygg, bygg- og entreprenørvirksomhet, eie, leie, kjøp, salg og drift av fast eiendom og alt som faller naturlig sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, samt kjøp og salg av aksjer og andre verdipapirer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −37,000
Equity
NOK 441,000
Est. value
NOK 716,000

Financial health · 2025

Liquidity
-0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.2%
Good
Equity as a share of total capital

Who owns KM EIENDOMSUTVIKLING AS?

TORSNES EIENDOMSSELSKAP AS
KM EIENDOMSUTVIKLING AS
· NOK −37,000 profit

KM EIENDOMSUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KM EIENDOMSUTVIKLING AS own?

KM EIENDOMSUTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KM EIENDOMSUTVIKLING AS

Who owns KM EIENDOMSUTVIKLING AS?

TORSNES EIENDOMSSELSKAP AS is the largest registered owner, with 100.0%.

Where is KM EIENDOMSUTVIKLING AS based?

KM EIENDOMSUTVIKLING AS has its business address in Fredrikstad.

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.