BIZTRAC BETA
Rental and operating of own or leased real estate

KONGSRUD EIENDOM AS

Org. no. 919486112 Limited company (AS) Lier Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −106,000
Equity NOK 5.0m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−106k kr).

KONGSRUD EIENDOM AS is registered as a limited company in Lier, Buskerud with organisation number 919486112. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom. Eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −106,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −106,000
Equity
NOK 5.0m
Est. value
NOK 25.7m

Financial health · 2025

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

Who owns KONGSRUD EIENDOM AS?

BERNHARD KONGSRUD
KONGSRUD EIENDOM AS
NOK 0 rev. · NOK −106,000 profit

KONGSRUD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGSRUD EIENDOM AS

Who owns KONGSRUD EIENDOM AS?

BERNHARD KONGSRUD is the largest registered owner, with 100.0%.

What is the revenue of KONGSRUD EIENDOM AS?

KONGSRUD EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of KONGSRUD EIENDOM AS?

Bernhard Kongsrud is registered as general manager of KONGSRUD EIENDOM AS.

Where is KONGSRUD EIENDOM AS based?

KONGSRUD EIENDOM AS has its business address in Lierstranda.

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.