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

HUITFELDTSGATE 19 BRL

Org. no. 915468292 Housing cooperative (BRL) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 9.7m
Operating profit NOK 7.3m
Equity NOK 59.2m
Incorporated 2015

HUITFELDTSGATE 19 BRL is registered as a housing cooperative in Oslo, Oslo with organisation number 915468292. 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”. The most recent filed accounts, for the 2025 financial year, show NOK 9.7m in revenue and NOK 7.3m in operating profit.

Key figures · 2025

Revenue
NOK 9.7m
Operating profit
NOK 7.3m
Equity
NOK 59.2m
Est. value
NOK 51.4m

Financial health · 2025

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

Who owns HUITFELDTSGATE 19 BRL?

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

Frequently asked questions about HUITFELDTSGATE 19 BRL

What is the revenue of HUITFELDTSGATE 19 BRL?

HUITFELDTSGATE 19 BRL had revenue of NOK 9.7m in 2025.

Where is HUITFELDTSGATE 19 BRL based?

HUITFELDTSGATE 19 BRL has its business address in Oslo.

Property

Business address Colbjørnsens gate 1, 0256 Oslo
Cadastral unit 301-213/57/0/0
Building Enebolig · 1 unit

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