BIZTRAC BETA
COMPANY REGISTER PROFILE
916772416 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

HOOL PANORAMA 1

Org. no. 916772416 Condominium flat owner (ESEK) Stryn Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 807,000
Operating profit NOK 177,000
Equity NOK 786,000
Incorporated 2015

HOOL PANORAMA 1 is registered as a condominium flat owner in Stryn, Vestland with organisation number 916772416. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2015. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2024 financial year, show NOK 807,000 in revenue and NOK 177,000 in operating profit.

Key figures · 2024

Revenue
NOK 807,000
Operating profit
NOK 177,000
Equity
NOK 786,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns HOOL PANORAMA 1?

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

Frequently asked questions about HOOL PANORAMA 1

What is the revenue of HOOL PANORAMA 1?

HOOL PANORAMA 1 had revenue of NOK 807,000 in 2024.

Where is HOOL PANORAMA 1 based?

HOOL PANORAMA 1 has its business address in Stryn.

Property

Business address Holevegen 34B, 6783 Stryn
Cadastral unit 4651-46/30/0/0
Building Tomannsbolig, vertikal · 2 units

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