BIZTRAC BETA
Other real estate activities on a fee or contract basis

ØSTERLIE HOLDING AS

Org. no. 921541848 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −191,000
Equity NOK 67.9m
Incorporated 2018
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−191k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ØSTERLIE HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921541848. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå investeringsvirksomhet, eiendomsforvaltning og annen virksomhet beslektet med denne.”.

Key figures · 2025

Operating profit
NOK −191,000
Equity
NOK 67.9m
Est. value
NOK 113.8m

Financial health · 2025

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

Who owns ØSTERLIE HOLDING AS?

O.Ø. HOLDING AS
ØSTERLIE HOLDING AS
· NOK −191,000 profit

ØSTERLIE HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ØSTERLIE HOLDING AS own?

ØSTERLIE HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ØSTERLIE HOLDING AS

Who owns ØSTERLIE HOLDING AS?

O.Ø. HOLDING AS is the largest registered owner, with 50.0%.

Where is ØSTERLIE HOLDING AS based?

ØSTERLIE HOLDING AS has its business address in Trondheim.

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.