biztrac. BETA
COMPANY REGISTER PROFILE
971438649 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

VESTLIÅSEN BOLIGSAMEIE

Org. no. 971438649 Condominium flat owner (ESEK) Oslo Incorporated 1972 Active
Ownership graph ↗
Revenue 2024 NOK 10.3m
Operating profit NOK 2.6m
Equity NOK −28.9m
Incorporated 1972

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−28,9 mill kr).

VESTLIÅSEN BOLIGSAMEIE is registered as a condominium flat owner in Oslo, Oslo with organisation number 971438649. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1972. The company's stated purpose is: “Ivareta felles interesser i forbindelse med drift og vedlikehold av eiendommen.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.3m in revenue and NOK 2.6m in operating profit.

Former names: VESTLIÅSEN BOL SAME V/EXCEL EIENDOMSFORVALTNING, VESTLIÅSEN BOLIGSAMEIE V/EXCEL EIENDOMSFORVALTNING

Key figures · 2024

Revenue
NOK 10.3m
▲ +11 %
Operating profit
NOK 2.6m
▼ −2 %
Equity
NOK −28.9m
▲ +2 %
Est. value
NOK 10.1m

Financial health · 2024

Liquidity
10.17
Very good
Current assets ÷ current liabilities
Profitability
72.3%
Very good
Return on total assets
Solidity
-823.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VESTLIÅSEN BOLIGSAMEIE?

No shareholders are registered for VESTLIÅSEN BOLIGSAMEIE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about VESTLIÅSEN BOLIGSAMEIE

What is the revenue of VESTLIÅSEN BOLIGSAMEIE?

VESTLIÅSEN BOLIGSAMEIE had revenue of NOK 10.3m in 2024.

Where is VESTLIÅSEN BOLIGSAMEIE based?

VESTLIÅSEN BOLIGSAMEIE has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.