BIZTRAC BETA
Rental and operating of own or leased real estate

ØSTENSJØVEIEN 43 AS

Org. no. 993085472 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK −900,000
Equity NOK 36.5m
Incorporated 2008
Share capital NOK 831,000

Signals

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

ØSTENSJØVEIEN 43 AS is registered as a limited company in Oslo, Oslo with organisation number 993085472. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 831,000, divided into 100 shares. The company's stated purpose is: “Erverve, utvikle og drifte fast eiendom, samt enhver annen virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK −900,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK −900,000
Equity
NOK 36.5m
Est. value
NOK 31.2m

Financial health · 2024

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

Who owns ØSTENSJØVEIEN 43 AS?

ENTRA BRYN AS
ØSTENSJØVEIEN 43 AS
NOK 4.1m rev. · NOK −900,000 profit

ØSTENSJØVEIEN 43 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØSTENSJØVEIEN 43 AS

Who owns ØSTENSJØVEIEN 43 AS?

ENTRA BRYN AS is the largest registered owner, with 100.0%.

What is the revenue of ØSTENSJØVEIEN 43 AS?

ØSTENSJØVEIEN 43 AS had revenue of NOK 4.1m in 2024.

Where is ØSTENSJØVEIEN 43 AS based?

ØSTENSJØVEIEN 43 AS has its business address in Oslo.

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.