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

HASSELØY BOLIGBYGGELAG AS

Org. no. 935595746 Limited company (AS) Haugesund Incorporated 1951 Active
Revenue 2025 NOK 839,000
Operating profit NOK −514,000
Equity NOK −2.2m
Incorporated 1951
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,2 mill kr).

HASSELØY BOLIGBYGGELAG AS is registered as a limited company in Haugesund, Rogaland with organisation number 935595746. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1951. Registered share capital is NOK 100,000, divided into 20 shares. The company's stated purpose is: “Skaffe aksjeeierne bruksrett til egen bolig i selskapets eiendom (borett) og å drive virksomhet som står i sammenheng med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 839,000 in revenue and NOK −514,000 in operating profit.

Key figures · 2025

Revenue
NOK 839,000
▲ +14 %
Operating profit
NOK −514,000
▼ −382 %
Equity
NOK −2.2m
▼ −44 %

Financial health · 2025

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

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

Who owns HASSELØY BOLIGBYGGELAG AS?

No shareholders are registered for HASSELØY BOLIGBYGGELAG AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HASSELØY BOLIGBYGGELAG AS

What is the revenue of HASSELØY BOLIGBYGGELAG AS?

HASSELØY BOLIGBYGGELAG AS had revenue of NOK 839,000 in 2025.

Where is HASSELØY BOLIGBYGGELAG AS based?

HASSELØY BOLIGBYGGELAG AS has its business address in Haugesund.

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.