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

TORVBAKKGATA BORETTSLAG

Org. no. 948556383 Housing cooperative (BRL) Oslo Incorporated 1983 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 225,000
Equity NOK 14.7m
Incorporated 1983

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

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 225,000
Equity
NOK 14.7m
Est. value
NOK 8.4m

Financial health · 2025

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

Who owns TORVBAKKGATA BORETTSLAG?

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

Frequently asked questions about TORVBAKKGATA BORETTSLAG

What is the revenue of TORVBAKKGATA BORETTSLAG?

TORVBAKKGATA BORETTSLAG had revenue of NOK 3.6m in 2025.

Where is TORVBAKKGATA BORETTSLAG based?

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