BIZTRAC BETA
Camping grounds and recreational vehicle parks

SOKN CAMPING AS

Org. no. 818717512 Limited company (AS) Stavanger Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 12.3m
Operating profit NOK −898,000
Equity NOK 995,000
Incorporated 2017
Employees 10
Share capital NOK 200,000

Signals

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

SOKN CAMPING AS is registered as a limited company in Stavanger, Rogaland with organisation number 818717512. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2017 and has 10 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Å drive eksisterende campingplass og marina på Sokn.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.3m in revenue and NOK −898,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.3m
Operating profit
NOK −898,000
Equity
NOK 995,000
Est. value
NOK 8.1m

Financial health · 2024

Liquidity
0.20
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.1%
Satisfactory
Equity as a share of total capital

Who owns SOKN CAMPING AS?

FRODE STANGELAND STEINE
SOKN CAMPING AS
NOK 12.3m rev. · NOK −898,000 profit

SOKN CAMPING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOKN CAMPING AS

Who owns SOKN CAMPING AS?

FRODE STANGELAND STEINE is the largest registered owner, with 25.0%.

What is the revenue of SOKN CAMPING AS?

SOKN CAMPING AS had revenue of NOK 12.3m in 2024.

Who is the general manager of SOKN CAMPING AS?

Frode Stangeland Steine is registered as general manager of SOKN CAMPING AS.

Where is SOKN CAMPING AS based?

SOKN CAMPING AS has its business address in Bru.

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.