BIZTRAC BETA
COMPANY REGISTER PROFILE
916378459 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

GUSTAV VIGELANDS VEI 2H BRL

Org. no. 916378459 Housing cooperative (BRL) Oslo Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK −105,000
Incorporated 2015

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−105k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

GUSTAV VIGELANDS VEI 2H BRL is registered as a housing cooperative in Oslo, Oslo with organisation number 916378459. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2015. The company's stated purpose is: “Borettslag”.

Key figures · 2025

Operating profit
NOK −16,000
Equity
NOK −105,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-10506.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GUSTAV VIGELANDS VEI 2H BRL?

No shareholders are registered for GUSTAV VIGELANDS VEI 2H BRL in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GUSTAV VIGELANDS VEI 2H BRL

Where is GUSTAV VIGELANDS VEI 2H BRL based?

GUSTAV VIGELANDS VEI 2H BRL has its business address in Oslo.

Property

Business address Gustav Vigelands vei 2H, 0274 Oslo
Cadastral unit 301-3/486/0/0
Building Enebolig · 1 unit

9 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.