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

SPIRE BORETTSLAG

Org. no. 928928586 Housing cooperative (BRL) Skien Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 3.5m
Equity NOK 517,000
Incorporated 2022

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

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 3.5m
Equity
NOK 517,000
Est. value
NOK 7.9m

Financial health · 2025

Liquidity
3.16
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 SPIRE BORETTSLAG?

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

Frequently asked questions about SPIRE BORETTSLAG

What is the revenue of SPIRE BORETTSLAG?

SPIRE BORETTSLAG had revenue of NOK 4.6m in 2025.

Where is SPIRE BORETTSLAG based?

SPIRE BORETTSLAG has its business address in Skien.

Property

Business address Hesselbergs gate 4, 3717 Skien
Cadastral unit 4003-300/1606/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

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