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

Borettslag Refne

Org. no. 948957949 Housing cooperative (BRL) Halden Incorporated 1975 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 1.8m
Equity NOK 6.6m
Incorporated 1975

Borettslag Refne is registered as a housing cooperative in Halden, Østfold with organisation number 948957949. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1975. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 1.8m
Equity
NOK 6.6m
Est. value
NOK 8.0m

Financial health · 2025

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

Who owns Borettslag Refne?

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

Frequently asked questions about Borettslag Refne

What is the revenue of Borettslag Refne?

Borettslag Refne had revenue of NOK 4.8m in 2025.

Where is Borettslag Refne based?

Borettslag Refne has its business address in Halden.

Property

Business address v/Halden Boligbyggelag Niels Stubs gate 6, 1776 Halden
Cadastral unit 3101-66/126/0/0
Building Annen kontorbygning · 10 units

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