BIZTRAC BETA
Development of building projects

KMMH EIENDOM AS

Org. no. 931434411 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 39,000
Operating profit NOK −96,000
Equity NOK −361,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−361k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−96k kr).

KMMH EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 931434411. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikling, drift, investering og salg av fast eiendom, investering i aksjer og verdiapirer, deltakelse i andre selskap og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 39,000 in revenue and NOK −96,000 in operating profit.

Key figures · 2024

Revenue
NOK 39,000
Operating profit
NOK −96,000
Equity
NOK −361,000

Financial health · 2024

Liquidity
5792.57
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-8.2%
Weak
Equity as a share of total capital

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

Who owns KMMH EIENDOM AS?

HAAKON ERDVIK
KMMH EIENDOM AS
NOK 39,000 rev. · NOK −96,000 profit

KMMH EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KMMH EIENDOM AS

Who owns KMMH EIENDOM AS?

HAAKON ERDVIK is the largest registered owner, with 25.0%.

What is the revenue of KMMH EIENDOM AS?

KMMH EIENDOM AS had revenue of NOK 39,000 in 2024.

Where is KMMH EIENDOM AS based?

KMMH EIENDOM AS has its business address in Kristiansand S.

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.