BIZTRAC BETA
Rental and operating of own or leased real estate

BERTEL O. STEEN EIENDOM HOLDING AS

Org. no. 927102552 Limited company (AS) Lørenskog Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −2.6m
Equity NOK 726.9m
Incorporated 2021
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,6 mill kr).

BERTEL O. STEEN EIENDOM HOLDING AS is registered as a limited company in Lørenskog, Akershus with organisation number 927102552. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Selskapets virksomhet er et investeringsselskap, herunder å investere i aksjer, fast eiendom, andeler i selskap og annet som står i naturlig forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −2.6m
Equity
NOK 726.9m
Est. value
NOK 580.9m

Financial health · 2024

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

Who owns BERTEL O. STEEN EIENDOM HOLDING AS?

BERTEL O. STEEN HOLDING AS
BERTEL O. STEEN EIENDOM HOLDING AS
· NOK −2.6m profit

BERTEL O. STEEN EIENDOM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BERTEL O. STEEN EIENDOM HOLDING AS own?

BERTEL O. STEEN EIENDOM HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about BERTEL O. STEEN EIENDOM HOLDING AS

Who owns BERTEL O. STEEN EIENDOM HOLDING AS?

BERTEL O. STEEN HOLDING AS is the largest registered owner, with 100.0%.

Where is BERTEL O. STEEN EIENDOM HOLDING AS based?

BERTEL O. STEEN EIENDOM HOLDING AS has its business address in Lørenskog.

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.