BIZTRAC BETA
Rental and operating of own or leased real estate

LERBERG EIENDOM AS

Org. no. 977374197 Limited company (AS) Øvre Eiker Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 1.5m
Equity NOK 5.1m
Incorporated 1997
Share capital NOK 600,000

LERBERG EIENDOM AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 977374197. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 600,000, divided into 30000 shares. The company's stated purpose is: “Eie fast eiendom, og drive utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 1.5m
Equity
NOK 5.1m
Est. value
NOK 6.3m

Financial health · 2025

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

Who owns LERBERG EIENDOM AS?

NILS IVAR BRAATHEN
LERBERG EIENDOM AS
NOK 2.8m rev. · NOK 1.5m profit

LERBERG EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LERBERG EIENDOM AS own?

LERBERG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LERBERG EIENDOM AS

Who owns LERBERG EIENDOM AS?

NILS IVAR BRAATHEN is the largest registered owner, with 76.7%.

What is the revenue of LERBERG EIENDOM AS?

LERBERG EIENDOM AS had revenue of NOK 2.8m in 2025.

Who is the general manager of LERBERG EIENDOM AS?

Nils Ivar Braathen is registered as general manager of LERBERG EIENDOM AS.

Where is LERBERG EIENDOM AS based?

LERBERG EIENDOM AS has its business address in Hokksund.

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.