BIZTRAC BETA
Rental and operating of own or leased real estate

M KLUNGLAND HOLDING AS

Org. no. 924900393 Limited company (AS) Kristiansand Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 211,000
Operating profit NOK 55,000
Equity NOK 15.5m
Incorporated 2020
Share capital NOK 60,000

M KLUNGLAND HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 924900393. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i aksjer og eiendom herunder deltakelse i andre selskaper samt alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 211,000 in revenue and NOK 55,000 in operating profit.

Key figures · 2025

Revenue
NOK 211,000
Operating profit
NOK 55,000
Equity
NOK 15.5m
Est. value
NOK 10.9m

Financial health · 2025

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

Who owns M KLUNGLAND HOLDING AS?

MORTEN KLUNGLAND
M KLUNGLAND HOLDING AS
NOK 211,000 rev. · NOK 55,000 profit

M KLUNGLAND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M KLUNGLAND HOLDING AS own?

M KLUNGLAND HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about M KLUNGLAND HOLDING AS

Who owns M KLUNGLAND HOLDING AS?

MORTEN KLUNGLAND is the largest registered owner, with 100.0%.

What is the revenue of M KLUNGLAND HOLDING AS?

M KLUNGLAND HOLDING AS had revenue of NOK 211,000 in 2025.

Where is M KLUNGLAND HOLDING AS based?

M KLUNGLAND HOLDING AS has its business address in Søgne.

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.