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

NEDRE BØEN BORETTSLAG

Org. no. 947429477 Housing cooperative (BRL) Tinn Incorporated 1975 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 799,000
Incorporated 1975

NEDRE BØEN BORETTSLAG is registered as a housing cooperative in Tinn, Telemark with organisation number 947429477. 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 5.3m in revenue and NOK 799,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 799,000
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

Who owns NEDRE BØEN BORETTSLAG?

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

Frequently asked questions about NEDRE BØEN BORETTSLAG

What is the revenue of NEDRE BØEN BORETTSLAG?

NEDRE BØEN BORETTSLAG had revenue of NOK 5.3m in 2025.

Where is NEDRE BØEN BORETTSLAG based?

NEDRE BØEN BORETTSLAG has its business address in Rjukan.

Property

Business address c/o RTBBL Storgata 19A, 3660 Rjukan
Cadastral unit 4026-125/135/0/0
Building Annen kontorbygning · 1 unit

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