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

STORGÅRDEN BORETTSLAG

Org. no. 950385529 Housing cooperative (BRL) Oslo Incorporated 1962 Active
Ownership graph ↗
Revenue 2025 NOK 34.5m
Operating profit NOK 10.1m
Equity NOK 40.0m
Incorporated 1962

STORGÅRDEN BORETTSLAG is registered as a housing cooperative in Oslo, Oslo with organisation number 950385529. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1962. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 34.5m in revenue and NOK 10.1m in operating profit.

Key figures · 2025

Revenue
NOK 34.5m
Operating profit
NOK 10.1m
Equity
NOK 40.0m
Est. value
NOK 49.1m

Financial health · 2025

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

Who owns STORGÅRDEN BORETTSLAG?

No shareholders are registered for STORGÅRDEN BORETTSLAG in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STORGÅRDEN BORETTSLAG

What is the revenue of STORGÅRDEN BORETTSLAG?

STORGÅRDEN BORETTSLAG had revenue of NOK 34.5m in 2025.

Where is STORGÅRDEN BORETTSLAG based?

STORGÅRDEN BORETTSLAG has its business address in Oslo.

Property

Business address v/OBOS Hammersborg torg 1, 0179 Oslo
Cadastral unit 301-208/279/0/0

1650 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.