BIZTRAC BETA
Rental and operating of own or leased real estate

KOLSTAD EIENDOM AS

Org. no. 989079204 Limited company (AS) Holmestrand Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 824,000
Operating profit NOK 219,000
Equity NOK 1.6m
Incorporated 2005
Share capital NOK 100,000

KOLSTAD EIENDOM AS is registered as a limited company in Holmestrand, Vestfold with organisation number 989079204. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling og forvaltning av fast eiendom samt annen virksomhet som står i sammenheng med dette, herunder også deltakelse av andre selskap med liknende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 824,000 in revenue and NOK 219,000 in operating profit.

Key figures · 2024

Revenue
NOK 824,000
Operating profit
NOK 219,000
Equity
NOK 1.6m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns KOLSTAD EIENDOM AS?

CORRECT EIENDOM AS
KOLSTAD EIENDOM AS
NOK 824,000 rev. · NOK 219,000 profit

KOLSTAD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOLSTAD EIENDOM AS

Who owns KOLSTAD EIENDOM AS?

CORRECT EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KOLSTAD EIENDOM AS?

KOLSTAD EIENDOM AS had revenue of NOK 824,000 in 2024.

Who is the general manager of KOLSTAD EIENDOM AS?

Olav Arnesson Løver is registered as general manager of KOLSTAD EIENDOM AS.

Where is KOLSTAD EIENDOM AS based?

KOLSTAD EIENDOM AS has its business address in Hof.

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.