BIZTRAC BETA
Rental and operating of own or leased real estate

ØSTREGATE 3 AS

Org. no. 925149020 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK 2.6m
Equity NOK 9.5m
Incorporated 2020
Share capital NOK 340,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ØSTREGATE 3 AS is registered as a limited company in Bærum, Akershus with organisation number 925149020. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 340,000, divided into 3000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK 2.6m
Equity
NOK 9.5m
Est. value
NOK 13.1m

Financial health · 2024

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

Who owns ØSTREGATE 3 AS?

FROGNEREIENDOM AS
ØSTREGATE 3 AS
NOK 4.7m rev. · NOK 2.6m profit

ØSTREGATE 3 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØSTREGATE 3 AS own?

ØSTREGATE 3 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØSTREGATE 3 AS

Who owns ØSTREGATE 3 AS?

FROGNEREIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ØSTREGATE 3 AS?

ØSTREGATE 3 AS had revenue of NOK 4.7m in 2024.

Where is ØSTREGATE 3 AS based?

ØSTREGATE 3 AS has its business address in Rud.

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.