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

TUNET BORETTSLAG

Org. no. 913303687 Housing cooperative (BRL) Stavanger Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 7.4m
Operating profit NOK 5.1m
Equity NOK 16.6m
Incorporated 2014

TUNET BORETTSLAG is registered as a housing cooperative in Stavanger, Rogaland with organisation number 913303687. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2014. The company's stated purpose is: “Borettslag”. The most recent filed accounts, for the 2025 financial year, show NOK 7.4m in revenue and NOK 5.1m in operating profit.

Key figures · 2025

Revenue
NOK 7.4m
Operating profit
NOK 5.1m
Equity
NOK 16.6m
Est. value
NOK 21.2m

Financial health · 2025

Liquidity
4.01
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.9%
Satisfactory
Equity as a share of total capital

Who owns TUNET BORETTSLAG?

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

Frequently asked questions about TUNET BORETTSLAG

What is the revenue of TUNET BORETTSLAG?

TUNET BORETTSLAG had revenue of NOK 7.4m in 2025.

Where is TUNET BORETTSLAG based?

TUNET BORETTSLAG has its business address in Stavanger.

Property

Business address Zetlitzveien 2, 4017 Stavanger
Cadastral unit 1103-20/37/0/0
Building Butikkbygning · 1 unit

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