biztrac. BETA
COMPANY REGISTER PROFILE
911899345 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other unspecified social services without accommodation

BLINDHEIM OG HATLEHOL HELSELAG

Org. no. 911899345 Association/club/organisation (FLI) Ålesund Incorporated 1922 Active
Revenue 2025 NOK 86,000
Operating profit NOK −11,000
Equity NOK 0
Incorporated 1922

Signals

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

BLINDHEIM OG HATLEHOL HELSELAG is registered as a association/club/organisation in Ålesund, Møre og Romsdal with organisation number 911899345. The business is classified under other unspecified social services without accommodation (NACE 88.996). The company was incorporated in 1922. The most recent filed accounts, for the 2025 financial year, show NOK 86,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 86,000
Operating profit
NOK −11,000
Equity
NOK 0

Financial health · 2023

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

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

Who owns BLINDHEIM OG HATLEHOL HELSELAG?

No shareholders are registered for BLINDHEIM OG HATLEHOL HELSELAG in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BLINDHEIM OG HATLEHOL HELSELAG

What is the revenue of BLINDHEIM OG HATLEHOL HELSELAG?

BLINDHEIM OG HATLEHOL HELSELAG had revenue of NOK 86,000 in 2025.

Who is the general manager of BLINDHEIM OG HATLEHOL HELSELAG?

Solveig Hauge is registered as general manager of BLINDHEIM OG HATLEHOL HELSELAG.

Where is BLINDHEIM OG HATLEHOL HELSELAG based?

BLINDHEIM OG HATLEHOL HELSELAG has its business address in Ålesund.

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.