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

VERPINGSVIKA BORETTSLAG

Org. no. 988435082 Housing cooperative (BRL) Ålesund Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.2m
Equity NOK 7.5m
Incorporated 2005

VERPINGSVIKA BORETTSLAG is registered as a housing cooperative in Ålesund, Møre og Romsdal with organisation number 988435082. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2005. The company's stated purpose is: “Borettslag”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.2m
Equity
NOK 7.5m
Est. value
NOK 7.1m

Financial health · 2025

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

Who owns VERPINGSVIKA BORETTSLAG?

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

Frequently asked questions about VERPINGSVIKA BORETTSLAG

What is the revenue of VERPINGSVIKA BORETTSLAG?

VERPINGSVIKA BORETTSLAG had revenue of NOK 1.9m in 2025.

Where is VERPINGSVIKA BORETTSLAG based?

VERPINGSVIKA BORETTSLAG has its business address in Ålesund.

Property

Business address Ystenesgata 6B, 6003 Ålesund
Cadastral unit 1508-201/752/0/0

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