BIZTRAC BETA
Rental and operating of own or leased real estate

BRYGGERIVEIEN 9 EIENDOM AS

Org. no. 930687510 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 13.8m
Operating profit NOK 6.1m
Equity NOK 188.4m
Incorporated 2023
Share capital NOK 30,000

Signals

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

BRYGGERIVEIEN 9 EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 930687510. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investering i eiendom og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.8m in revenue and NOK 6.1m in operating profit.

Key figures · 2025

Revenue
NOK 13.8m
Operating profit
NOK 6.1m
Equity
NOK 188.4m
Est. value
NOK 149.6m

Financial health · 2025

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

Who owns BRYGGERIVEIEN 9 EIENDOM AS?

BRYGGERIVEIEN 9 INVEST AS
BRYGGERIVEIEN 9 EIENDOM AS
NOK 13.8m rev. · NOK 6.1m profit

BRYGGERIVEIEN 9 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRYGGERIVEIEN 9 EIENDOM AS

Who owns BRYGGERIVEIEN 9 EIENDOM AS?

BRYGGERIVEIEN 9 INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BRYGGERIVEIEN 9 EIENDOM AS?

BRYGGERIVEIEN 9 EIENDOM AS had revenue of NOK 13.8m in 2025.

Where is BRYGGERIVEIEN 9 EIENDOM AS based?

BRYGGERIVEIEN 9 EIENDOM AS has its business address in Lysaker.

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.