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

ØRNKLOA BORETTSLAG

Org. no. 950150998 Housing cooperative (BRL) Vågan Incorporated 1975 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 406,000
Equity NOK 3.7m
Incorporated 1975

ØRNKLOA BORETTSLAG is registered as a housing cooperative in Vågan, Nordland with organisation number 950150998. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1975. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 406,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 406,000
Equity
NOK 3.7m
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns ØRNKLOA BORETTSLAG?

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

Frequently asked questions about ØRNKLOA BORETTSLAG

What is the revenue of ØRNKLOA BORETTSLAG?

ØRNKLOA BORETTSLAG had revenue of NOK 1.2m in 2025.

Where is ØRNKLOA BORETTSLAG based?

ØRNKLOA BORETTSLAG has its business address in Svolvær.

Property

Business address Falkveien 10, 8300 Svolvær
Cadastral unit 1865-16/138/0/0
Building Kjede/atriumhus · 3 units

3 companies are registered at this address.

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.