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

INGOLFSLAND BORETTSLAG

Org. no. 931990756 Housing cooperative (BRL) Tinn Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK 885,000
Incorporated 1982

INGOLFSLAND BORETTSLAG is registered as a housing cooperative in Tinn, Telemark with organisation number 931990756. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1982. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 885,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK 885,000
Est. value
NOK 3.5m

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 INGOLFSLAND BORETTSLAG?

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

Frequently asked questions about INGOLFSLAND BORETTSLAG

What is the revenue of INGOLFSLAND BORETTSLAG?

INGOLFSLAND BORETTSLAG had revenue of NOK 4.2m in 2025.

Where is INGOLFSLAND BORETTSLAG based?

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