BIZTRAC BETA
Rental and operating of own or leased real estate

LINDEBERG EIENDOM AS

Org. no. 941964214 Limited company (AS) Lillestrøm Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 8.8m
Operating profit NOK 3.4m
Equity NOK 30.3m
Incorporated 1987
Share capital NOK 1.0m

LINDEBERG EIENDOM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 941964214. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Drive med kjøp, utleie og salg av eiendom, eller eierskap i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.8m in revenue and NOK 3.4m in operating profit.

Key figures · 2024

Revenue
NOK 8.8m
Operating profit
NOK 3.4m
Equity
NOK 30.3m
Est. value
NOK 28.0m

Financial health · 2024

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

Who owns LINDEBERG EIENDOM AS?

BRENNSUND HOLDING AS
LINDEBERG EIENDOM AS
NOK 8.8m rev. · NOK 3.4m profit

LINDEBERG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LINDEBERG EIENDOM AS own?

LINDEBERG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Group structure

LINDEBERG EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about LINDEBERG EIENDOM AS

Who owns LINDEBERG EIENDOM AS?

BRENNSUND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LINDEBERG EIENDOM AS?

LINDEBERG EIENDOM AS had revenue of NOK 8.8m in 2024.

Where is LINDEBERG EIENDOM AS based?

LINDEBERG EIENDOM AS has its business address in Frogner.

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.