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

SENTRUMSPARKEN ÅL 2 BURETTSLAG

Org. no. 934226003 Housing cooperative (BRL) Ål Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK 37,000
Incorporated 2024

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

SENTRUMSPARKEN ÅL 2 BURETTSLAG is registered as a housing cooperative in Ål, Buskerud with organisation number 934226003. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2024. The company's stated purpose is: “Borettslag”.

Key figures · 2025

Operating profit
NOK −19,000
Equity
NOK 37,000
Est. value
NOK 43,000

Financial health · 2025

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

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

Who owns SENTRUMSPARKEN ÅL 2 BURETTSLAG?

No shareholders are registered for SENTRUMSPARKEN ÅL 2 BURETTSLAG in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SENTRUMSPARKEN ÅL 2 BURETTSLAG

Where is SENTRUMSPARKEN ÅL 2 BURETTSLAG based?

SENTRUMSPARKEN ÅL 2 BURETTSLAG has its business address in Torpo.

Property

Business address C/O Hallingdal Hytteservice AS Torpovegen 304, 3579 Torpo
Cadastral unit 3328-8/86/0/0
Building Fabrikkbygning · 1 unit

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