BIZTRAC BETA
Rental and operating of own or leased real estate

KK EIENDOM HOLDING AS

Org. no. 931663798 Limited company (AS) Ringebu Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −20,000
Equity NOK 4.7m
Incorporated 2023
Share capital NOK 225,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−20k kr).

KK EIENDOM HOLDING AS is registered as a limited company in Ringebu, Innlandet with organisation number 931663798. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 225,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper og virksomhet i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 4.7m
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns KK EIENDOM HOLDING AS?

MAD INVEST AS
KK EIENDOM HOLDING AS
NOK 0 rev. · NOK −20,000 profit

KK EIENDOM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KK EIENDOM HOLDING AS own?

KK EIENDOM HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KK EIENDOM HOLDING AS

Who owns KK EIENDOM HOLDING AS?

MAD INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of KK EIENDOM HOLDING AS?

KK EIENDOM HOLDING AS had revenue of NOK 0 in 2024.

Where is KK EIENDOM HOLDING AS based?

KK EIENDOM HOLDING AS has its business address in Ringebu.

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.