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

HAVNEGÅRDEN BORETTSLAG

Org. no. 917365539 Housing cooperative (BRL) Larvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.3m
Equity NOK 633,000
Incorporated 2016

HAVNEGÅRDEN BORETTSLAG is registered as a housing cooperative in Larvik, Vestfold with organisation number 917365539. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2016. The company's stated purpose is: “Borettslag”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 1.3m
Equity
NOK 633,000
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns HAVNEGÅRDEN BORETTSLAG?

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

Frequently asked questions about HAVNEGÅRDEN BORETTSLAG

What is the revenue of HAVNEGÅRDEN BORETTSLAG?

HAVNEGÅRDEN BORETTSLAG had revenue of NOK 2.6m in 2025.

Where is HAVNEGÅRDEN BORETTSLAG based?

HAVNEGÅRDEN BORETTSLAG has its business address in Larvik.

Property

Business address Prinsegata 4, 3256 Larvik
Cadastral unit 3909-3020/1578/0/0

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