biztrac. BETA
COMPANY REGISTER PROFILE
934095863 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

ULLEVÅLSALLEEN 5 BORETTSLAG.

Org. no. 934095863 Housing cooperative (BRL) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 451,000
Operating profit NOK −1.1m
Equity NOK −204.7m
Incorporated 2024

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−204,7 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,1 mill kr).
  • Nylig endring 2026-09-07 Adresseendring registrert 2026-09-07.

ULLEVÅLSALLEEN 5 BORETTSLAG. is registered as a housing cooperative in Oslo, Oslo with organisation number 934095863. 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”. The most recent filed accounts, for the 2025 financial year, show NOK 451,000 in revenue and NOK −1.1m in operating profit.

Key figures · 2025

Revenue
NOK 451,000
▼ −96 %
Operating profit
NOK −1.1m
▼ −115 %
Equity
NOK −204.7m
▲ +0 %
Est. value
NOK 10.3m

Financial health · 2025

Liquidity
7.33
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-433.0%
Weak
Equity as a share of total capital

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

Who owns ULLEVÅLSALLEEN 5 BORETTSLAG.?

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

Frequently asked questions about ULLEVÅLSALLEEN 5 BORETTSLAG.

What is the revenue of ULLEVÅLSALLEEN 5 BORETTSLAG.?

ULLEVÅLSALLEEN 5 BORETTSLAG. had revenue of NOK 451,000 in 2025.

Where is ULLEVÅLSALLEEN 5 BORETTSLAG. based?

ULLEVÅLSALLEEN 5 BORETTSLAG. has its business address in Oslo.

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

Report a problem

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