BIZTRAC BETA
Rental and operating of own or leased real estate

KROHNSTAD BOLIGEIENDOM AS

Org. no. 986923942 Limited company (AS) Bergen Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 5.4m
Operating profit NOK 3.1m
Equity NOK 4.3m
Incorporated 2004
Employees 7
Share capital NOK 1.0m

KROHNSTAD BOLIGEIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 986923942. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004 and has 7 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering i og utleie av fast eiendom. Selskapet kan også delta i andre virksomheter. ”. The most recent filed accounts, for the 2025 financial year, show NOK 5.4m in revenue and NOK 3.1m in operating profit.

Key figures · 2025

Revenue
NOK 5.4m
Operating profit
NOK 3.1m
Equity
NOK 4.3m
Est. value
NOK 5.9m

Financial health · 2025

Liquidity
0.21
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.4%
Weak
Equity as a share of total capital

Who owns KROHNSTAD BOLIGEIENDOM AS?

RUNAR EIKHAUG
KROHNSTAD BOLIGEIENDOM AS
NOK 5.4m rev. · NOK 3.1m profit

KROHNSTAD BOLIGEIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KROHNSTAD BOLIGEIENDOM AS

Who owns KROHNSTAD BOLIGEIENDOM AS?

RUNAR EIKHAUG is the largest registered owner, with 40.0%.

What is the revenue of KROHNSTAD BOLIGEIENDOM AS?

KROHNSTAD BOLIGEIENDOM AS had revenue of NOK 5.4m in 2025.

Who is the general manager of KROHNSTAD BOLIGEIENDOM AS?

Runar Eikhaug is registered as general manager of KROHNSTAD BOLIGEIENDOM AS.

Where is KROHNSTAD BOLIGEIENDOM AS based?

KROHNSTAD BOLIGEIENDOM AS has its business address in Nesttun.

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.