BIZTRAC BETA
Rental and operating of own or leased real estate

BRUVIN PARK II AS

Org. no. 992601272 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −906,000
Equity NOK 15.0m
Incorporated 2008
Share capital NOK 1.5m

Signals

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

BRUVIN PARK II AS is registered as a limited company in Oslo, Oslo with organisation number 992601272. 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 1.5m, divided into 30000 shares. The company's stated purpose is: “Forvaltning og drift av eiendom samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −906,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −906,000
Equity
NOK 15.0m
Est. value
NOK 13.7m

Financial health · 2024

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.8%
Good
Equity as a share of total capital

Who owns BRUVIN PARK II AS?

MAYA BOLIG 3 AS
BRUVIN PARK II AS
NOK 1.1m rev. · NOK −906,000 profit

BRUVIN PARK II AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BRUVIN PARK II AS er morselskap for 48 datterselskaper:

Frequently asked questions about BRUVIN PARK II AS

Who owns BRUVIN PARK II AS?

MAYA BOLIG 3 AS is the largest registered owner, with 100.0%.

What is the revenue of BRUVIN PARK II AS?

BRUVIN PARK II AS had revenue of NOK 1.1m in 2024.

Where is BRUVIN PARK II AS based?

BRUVIN PARK II 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.