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

JONASHAGEN 2 BORETTSLAG

Org. no. 935026296 Housing cooperative (BRL) Stavanger Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −46,000
Equity NOK −218
Incorporated 2024

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−218 kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−46k kr).

JONASHAGEN 2 BORETTSLAG is registered as a housing cooperative in Stavanger, Rogaland with organisation number 935026296. 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 −46,000
Equity
NOK −218

Financial health · 2025

Liquidity
0.97
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.0%
Weak
Equity as a share of total capital

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

Who owns JONASHAGEN 2 BORETTSLAG?

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

Frequently asked questions about JONASHAGEN 2 BORETTSLAG

Where is JONASHAGEN 2 BORETTSLAG based?

JONASHAGEN 2 BORETTSLAG has its business address in Stavanger.

Property

Business address c/o Bate boligbyggelag Zetlitzveien 2, 4017 Stavanger
Cadastral unit 1103-20/37/0/0
Building Butikkbygning · 1 unit

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