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

BLÅTIND BORETTSLAG

Org. no. 914916631 Housing cooperative (BRL) Vågan Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 956,000
Operating profit NOK 564,000
Equity NOK 326,000
Incorporated 2014

BLÅTIND BORETTSLAG is registered as a housing cooperative in Vågan, Nordland with organisation number 914916631. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2014. The company's stated purpose is: “Borettslag”. The most recent filed accounts, for the 2025 financial year, show NOK 956,000 in revenue and NOK 564,000 in operating profit.

Key figures · 2025

Revenue
NOK 956,000
Operating profit
NOK 564,000
Equity
NOK 326,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns BLÅTIND BORETTSLAG?

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

Frequently asked questions about BLÅTIND BORETTSLAG

What is the revenue of BLÅTIND BORETTSLAG?

BLÅTIND BORETTSLAG had revenue of NOK 956,000 in 2025.

Where is BLÅTIND BORETTSLAG based?

BLÅTIND BORETTSLAG has its business address in Svolvær.

Property

Business address Garsosveien 42A, 8300 Svolvær
Cadastral unit 1865-18/2203/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 3 units

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.