BIZTRAC BETA
Other recreational activities

ØYGARDEN OPPLEVELSESSENTER AS

Org. no. 929777166 Limited company (AS) Øygarden Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −47,000
Equity NOK −22,000
Incorporated 2022
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−22k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−47k kr).

ØYGARDEN OPPLEVELSESSENTER AS is registered as a limited company in Øygarden, Vestland with organisation number 929777166. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av båtplasser og lokaler til firma som tilbyr opplevelser.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −47,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −47,000
Equity
NOK −22,000

Financial health · 2024

Liquidity
0.67
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-49.2%
Weak
Equity as a share of total capital

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

Who owns ØYGARDEN OPPLEVELSESSENTER AS?

GEIR-ATLE VIK
ØYGARDEN OPPLEVELSESSENTER AS
NOK 0 rev. · NOK −47,000 profit

ØYGARDEN OPPLEVELSESSENTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØYGARDEN OPPLEVELSESSENTER AS

Who owns ØYGARDEN OPPLEVELSESSENTER AS?

GEIR-ATLE VIK is the largest registered owner, with 50.0%.

What is the revenue of ØYGARDEN OPPLEVELSESSENTER AS?

ØYGARDEN OPPLEVELSESSENTER AS had revenue of NOK 0 in 2024.

Where is ØYGARDEN OPPLEVELSESSENTER AS based?

ØYGARDEN OPPLEVELSESSENTER AS has its business address in Rong.

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.