BIZTRAC BETA
Rental and operating of own or leased real estate

HYLLESTAD UTVIKLINGSPARK AS

Org. no. 897505142 Limited company (AS) Hyllestad Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 579,000
Operating profit NOK 270,000
Equity NOK 2.5m
Incorporated 2011
Share capital NOK 3.0m

HYLLESTAD UTVIKLINGSPARK AS is registered as a limited company in Hyllestad, Vestland with organisation number 897505142. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 3.0m, divided into 1081620 shares. The company's stated purpose is: “Erverve, forvalte og realisere fast eigedom, her medrekna å erverve, opparbeide og forvalte næringsareal til bruk for nye og etablerte verksemder som kan skape nye aktiviteter og arbeidsplasser i kommunen.”. The most recent filed accounts, for the 2024 financial year, show NOK 579,000 in revenue and NOK 270,000 in operating profit.

Key figures · 2024

Revenue
NOK 579,000
Operating profit
NOK 270,000
Equity
NOK 2.5m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns HYLLESTAD UTVIKLINGSPARK AS?

HYLLESTAD KOMMUNE
HYLLESTAD UTVIKLINGSPARK AS
NOK 579,000 rev. · NOK 270,000 profit

HYLLESTAD UTVIKLINGSPARK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HYLLESTAD UTVIKLINGSPARK AS

Who owns HYLLESTAD UTVIKLINGSPARK AS?

HYLLESTAD KOMMUNE is the largest registered owner, with 65.7%.

What is the revenue of HYLLESTAD UTVIKLINGSPARK AS?

HYLLESTAD UTVIKLINGSPARK AS had revenue of NOK 579,000 in 2024.

Where is HYLLESTAD UTVIKLINGSPARK AS based?

HYLLESTAD UTVIKLINGSPARK AS has its business address in Hyllestad.

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

Report a problem

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