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

LADEVANGEN BORETTSLAG

Org. no. 875599992 Housing cooperative (BRL) Averøy Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 340,000
Equity NOK 7.0m
Incorporated 1986

LADEVANGEN BORETTSLAG is registered as a housing cooperative in Averøy, Møre og Romsdal with organisation number 875599992. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1986. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 340,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 340,000
Equity
NOK 7.0m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns LADEVANGEN BORETTSLAG?

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

Frequently asked questions about LADEVANGEN BORETTSLAG

What is the revenue of LADEVANGEN BORETTSLAG?

LADEVANGEN BORETTSLAG had revenue of NOK 1.5m in 2025.

Where is LADEVANGEN BORETTSLAG based?

LADEVANGEN BORETTSLAG has its business address in Averøy.

Property

Business address c/o Bjørn Karstein Røsand Blåbærstien 8, 6530 Averøy
Cadastral unit 1554-53/101/0/0
Building Enebolig · 1 unit

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.