BIZTRAC BETA
Rental and operating of own or leased real estate

HOLEMOEN EIENDOM AS

Org. no. 921335776 Limited company (AS) Modum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 216,000
Operating profit NOK 53,000
Equity NOK 541,000
Incorporated 2018
Share capital NOK 30,000

HOLEMOEN EIENDOM AS is registered as a limited company in Modum, Buskerud with organisation number 921335776. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utleie, utvikling og drift av fast eiendom samt oppføring, utvikling og salg av eiendom herunder det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 216,000 in revenue and NOK 53,000 in operating profit.

Key figures · 2025

Revenue
NOK 216,000
Operating profit
NOK 53,000
Equity
NOK 541,000
Est. value
NOK 461,000

Financial health · 2025

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

Who owns HOLEMOEN EIENDOM AS?

T.L.I NÆRING OG DRIFT AS
HOLEMOEN EIENDOM AS
NOK 216,000 rev. · NOK 53,000 profit

HOLEMOEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOLEMOEN EIENDOM AS

Who owns HOLEMOEN EIENDOM AS?

T.L.I NÆRING OG DRIFT AS is the largest registered owner, with 50.0%.

What is the revenue of HOLEMOEN EIENDOM AS?

HOLEMOEN EIENDOM AS had revenue of NOK 216,000 in 2025.

Who is the general manager of HOLEMOEN EIENDOM AS?

Trond Harald Thorrud is registered as general manager of HOLEMOEN EIENDOM AS.

Where is HOLEMOEN EIENDOM AS based?

HOLEMOEN EIENDOM AS has its business address in Vikersund.

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.