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

LANGVANN BORETTSLAG SULITJELMA

Org. no. 953532832 Housing cooperative (BRL) Fauske Incorporated 1966 Active
Ownership graph ↗
Revenue 2025 NOK 854,000
Operating profit NOK −697,000
Equity NOK −625,000
Incorporated 1966

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−625k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−697k kr).
  • Nylig endring 2026-05-08 Adresseendring registrert 2026-05-08.

LANGVANN BORETTSLAG SULITJELMA is registered as a housing cooperative in Fauske, Nordland with organisation number 953532832. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1966. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 854,000 in revenue and NOK −697,000 in operating profit.

Key figures · 2025

Revenue
NOK 854,000
▲ +14 %
Operating profit
NOK −697,000
▲ +42 %
Equity
NOK −625,000
▼ −520 %

Financial health · 2025

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

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

Who owns LANGVANN BORETTSLAG SULITJELMA?

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

Frequently asked questions about LANGVANN BORETTSLAG SULITJELMA

What is the revenue of LANGVANN BORETTSLAG SULITJELMA?

LANGVANN BORETTSLAG SULITJELMA had revenue of NOK 854,000 in 2025.

Where is LANGVANN BORETTSLAG SULITJELMA based?

LANGVANN BORETTSLAG SULITJELMA has its business address in Sulitjelma.

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.