BIZTRAC BETA
Rental and operating of own or leased real estate

HINNA PARK INVEST AS

Org. no. 992034602 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 136.2m
Operating profit NOK 99.7m
Equity NOK 2.3m
Incorporated 2007
Share capital NOK 901,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HINNA PARK INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 992034602. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 901,000, divided into 10000 shares. The company's stated purpose is: “Eie eiendommen gnr. 16, bnr. 1479 og 1480 i Stavanger kommune, og gjennom dette eierskap drifte og utvikle eiendommen, samt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 136.2m in revenue and NOK 99.7m in operating profit.

Key figures · 2024

Revenue
NOK 136.2m
Operating profit
NOK 99.7m
Equity
NOK 2.3m
Est. value
NOK 116.4m

Financial health · 2024

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

Who owns HINNA PARK INVEST AS?

H.I.G. PETRO II AS
HINNA PARK INVEST AS
NOK 136.2m rev. · NOK 99.7m profit

HINNA PARK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HINNA PARK INVEST AS

Who owns HINNA PARK INVEST AS?

H.I.G. PETRO II AS is the largest registered owner, with 100.0%.

What is the revenue of HINNA PARK INVEST AS?

HINNA PARK INVEST AS had revenue of NOK 136.2m in 2024.

Where is HINNA PARK INVEST AS based?

HINNA PARK INVEST AS has its business address in Oslo.

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.