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

LUNDHAUGEN BORETTSLAG

Org. no. 821189322 Housing cooperative (BRL) Senja Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 2.7m
Equity NOK 4.7m
Incorporated 2018

LUNDHAUGEN BORETTSLAG is registered as a housing cooperative in Senja, Troms with organisation number 821189322. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2018. The company's stated purpose is: “Borettslag”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 2.7m
Equity
NOK 4.7m
Est. value
NOK 8.3m

Financial health · 2025

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

Who owns LUNDHAUGEN BORETTSLAG?

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

Frequently asked questions about LUNDHAUGEN BORETTSLAG

What is the revenue of LUNDHAUGEN BORETTSLAG?

LUNDHAUGEN BORETTSLAG had revenue of NOK 4.4m in 2025.

Where is LUNDHAUGEN BORETTSLAG based?

LUNDHAUGEN BORETTSLAG has its business address in Finnsnes.

Property

Business address Ringveien 49, 9300 Finnsnes
Cadastral unit 5530-44/1230/0/0
Building Kjøpesenter, varehus · 40 units

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