BIZTRAC BETA
Development of building projects

ØYGARDEN II AS

Org. no. 924419474 Limited company (AS) Kristiansand Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK −71,000
Equity NOK 502,000
Incorporated 2019
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−71k kr).

ØYGARDEN II AS is registered as a limited company in Kristiansand, Agder with organisation number 924419474. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 400,000, divided into 1000 shares. The company's stated purpose is: “Drive eiendomsutvikling på prosjekt Øygarden i Lillesand kommune, samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK −71,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK −71,000
Equity
NOK 502,000
Est. value
NOK 7.0m

Financial health · 2024

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.5%
Weak
Equity as a share of total capital

Who owns ØYGARDEN II AS?

HELLVIK HUS SØGNE PROSJEKT AS
ØYGARDEN II AS
NOK 4.6m rev. · NOK −71,000 profit

ØYGARDEN II AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØYGARDEN II AS

Who owns ØYGARDEN II AS?

HELLVIK HUS SØGNE PROSJEKT AS is the largest registered owner, with 50.0%.

What is the revenue of ØYGARDEN II AS?

ØYGARDEN II AS had revenue of NOK 4.6m in 2024.

Who is the general manager of ØYGARDEN II AS?

Per Gudbrand Nome Try is registered as general manager of ØYGARDEN II AS.

Where is ØYGARDEN II AS based?

ØYGARDEN II AS has its business address in Søgne.

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.