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

LIEKVARTALET BORETTSLAG

Org. no. 985840962 Housing cooperative (BRL) Skien Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 930,000
Equity NOK 12.6m
Incorporated 2003

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

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 930,000
Equity
NOK 12.6m
Est. value
NOK 8.9m

Financial health · 2025

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

Who owns LIEKVARTALET BORETTSLAG?

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

Frequently asked questions about LIEKVARTALET BORETTSLAG

What is the revenue of LIEKVARTALET BORETTSLAG?

LIEKVARTALET BORETTSLAG had revenue of NOK 2.9m in 2025.

Where is LIEKVARTALET BORETTSLAG based?

LIEKVARTALET BORETTSLAG has its business address in Skien.

Property

Business address Cappelens gate 11, 3717 Skien
Cadastral unit 4003-300/682/0/0

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