BIZTRAC BETA
Camping grounds and recreational vehicle parks

KINSARVIK CAMPING AS

Org. no. 991436235 Limited company (AS) Ullensvang Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK 2.4m
Equity NOK 14.7m
Incorporated 2007
Employees 6
Share capital NOK 100,000

KINSARVIK CAMPING AS is registered as a limited company in Ullensvang, Vestland with organisation number 991436235. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2007 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av campingplass, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK 2.4m
Equity
NOK 14.7m
Est. value
NOK 15.5m

Financial health · 2024

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

Who owns KINSARVIK CAMPING AS?

EVALD SANDVIK HATTEN
KINSARVIK CAMPING AS
NOK 10.7m rev. · NOK 2.4m profit

KINSARVIK CAMPING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KINSARVIK CAMPING AS own?

KINSARVIK CAMPING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KINSARVIK CAMPING AS

Who owns KINSARVIK CAMPING AS?

EVALD SANDVIK HATTEN is the largest registered owner, with 100.0%.

What is the revenue of KINSARVIK CAMPING AS?

KINSARVIK CAMPING AS had revenue of NOK 10.7m in 2024.

Where is KINSARVIK CAMPING AS based?

KINSARVIK CAMPING AS has its business address in Kinsarvik.

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.