BIZTRAC BETA
Development of building projects

KIKUT EIENDOM AS

Org. no. 974684470 Limited company (AS) Hol Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 6.1m
Operating profit NOK 2.3m
Equity NOK 284.5m
Incorporated 1995
Share capital NOK 2.2m

KIKUT EIENDOM AS is registered as a limited company in Hol, Buskerud with organisation number 974684470. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1995. Registered share capital is NOK 2.2m, divided into 8000 shares. The company's stated purpose is: “Utvikling, salg og utleie av eiendom og annet som naturlig hører inn under dette, samt handel med aksjer og verdipapirer.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.1m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 6.1m
Operating profit
NOK 2.3m
Equity
NOK 284.5m
Est. value
NOK 199.1m

Financial health · 2024

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

Who owns KIKUT EIENDOM AS?

ARNE PÅLGARDHAUGEN
KIKUT EIENDOM AS
NOK 6.1m rev. · NOK 2.3m profit

KIKUT EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KIKUT EIENDOM AS own?

KIKUT EIENDOM AS holds stakes in 10 companies:

See the full ownership structure →

Frequently asked questions about KIKUT EIENDOM AS

Who owns KIKUT EIENDOM AS?

ARNE PÅLGARDHAUGEN is the largest registered owner, with 64.0%.

What is the revenue of KIKUT EIENDOM AS?

KIKUT EIENDOM AS had revenue of NOK 6.1m in 2024.

Who is the general manager of KIKUT EIENDOM AS?

Arne Pålgardhaugen is registered as general manager of KIKUT EIENDOM AS.

Where is KIKUT EIENDOM AS based?

KIKUT EIENDOM AS has its business address in Geilo.

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.