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

SKJERVA BORETTSLAG

Org. no. 925394459 Housing cooperative (BRL) Bodø Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 1.4m
Equity NOK 495,000
Incorporated 2020

SKJERVA BORETTSLAG is registered as a housing cooperative in Bodø, Nordland with organisation number 925394459. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2020. The company's stated purpose is: “Borettslag”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 1.4m
Equity
NOK 495,000
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns SKJERVA BORETTSLAG?

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

Frequently asked questions about SKJERVA BORETTSLAG

What is the revenue of SKJERVA BORETTSLAG?

SKJERVA BORETTSLAG had revenue of NOK 2.1m in 2025.

Where is SKJERVA BORETTSLAG based?

SKJERVA BORETTSLAG has its business address in Bodø.

Property

Business address Torvgata 2, 8006 Bodø
Cadastral unit 1804-138/50/0/0
Building Annen kontorbygning · 2 units

82 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.