biztrac. BETA
COMPANY REGISTER PROFILE
944332065 ORG. NO. 2021 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HAUGESUND SANITETSFORENING

Org. no. 944332065 Association/club/organisation (FLI) Haugesund Incorporated 1906 Active
Ownership graph ↗
Revenue 2021 NOK 436,000
Operating profit NOK −333,000
Equity NOK 115.4m
Incorporated 1906

Signals

1 flags
  • Driftsunderskudd 2021 Siste driftsresultat er negativt (−333k kr).

HAUGESUND SANITETSFORENING is registered as a association/club/organisation in Haugesund, Rogaland with organisation number 944332065. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1906. The most recent filed accounts, for the 2021 financial year, show NOK 436,000 in revenue and NOK −333,000 in operating profit.

Former names: HAUGESUND SANITETSFORENING (FORENING)

Key figures · 2021

Revenue
NOK 436,000
▲ +1 %
Operating profit
NOK −333,000
▲ +51 %
Equity
NOK 115.4m
▼ −2 %
Est. value
NOK 79.6m

Financial health · 2021

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

Who owns HAUGESUND SANITETSFORENING?

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

Which companies does HAUGESUND SANITETSFORENING own?

HAUGESUND SANITETSFORENING holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAUGESUND SANITETSFORENING

What is the revenue of HAUGESUND SANITETSFORENING?

HAUGESUND SANITETSFORENING had revenue of NOK 436,000 in 2021.

Where is HAUGESUND SANITETSFORENING based?

HAUGESUND SANITETSFORENING 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.