BIZTRAC BETA
Camping grounds and recreational vehicle parks

OGGE GJESTEHEIM AS

Org. no. 933363864 Limited company (AS) Iveland Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 412,000
Operating profit NOK −1,000
Equity NOK 23,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

OGGE GJESTEHEIM AS is registered as a limited company in Iveland, Agder with organisation number 933363864. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift og utvikling av camping, kiosk og serveringssted. Utleie av friluftsliv utstyr og festsal/møterom/kjøkken. Salg av varer og tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 412,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2024

Revenue
NOK 412,000
Operating profit
NOK −1,000
Equity
NOK 23,000
Est. value
NOK 228,000

Financial health · 2024

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

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

Who owns OGGE GJESTEHEIM AS?

LINDA TEN NAPEL BRIÉT
OGGE GJESTEHEIM AS
NOK 412,000 rev. · NOK −1,000 profit

OGGE GJESTEHEIM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OGGE GJESTEHEIM AS

Who owns OGGE GJESTEHEIM AS?

LINDA TEN NAPEL BRIÉT is the largest registered owner, with 51.0%.

What is the revenue of OGGE GJESTEHEIM AS?

OGGE GJESTEHEIM AS had revenue of NOK 412,000 in 2024.

Where is OGGE GJESTEHEIM AS based?

OGGE GJESTEHEIM AS has its business address in Vatnestrøm.

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.