BIZTRAC BETA
Camping grounds and recreational vehicle parks

LO-VIK CAMPING AS

Org. no. 989991612 Limited company (AS) Stryn Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK 250,000
Equity NOK 8.4m
Incorporated 2006
Share capital NOK 1.0m

LO-VIK CAMPING AS is registered as a limited company in Stryn, Vestland with organisation number 989991612. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2006. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Drift av campingplassar samt verksemd i tilknyting til dette, her medrekna deltaking i andre selskap med liknande formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK 250,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK 250,000
Equity
NOK 8.4m
Est. value
NOK 5.4m

Financial health · 2024

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

Who owns LO-VIK CAMPING AS?

KJELL LOEN
LO-VIK CAMPING AS
NOK 3.2m rev. · NOK 250,000 profit

LO-VIK CAMPING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LO-VIK CAMPING AS own?

LO-VIK CAMPING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LO-VIK CAMPING AS

Who owns LO-VIK CAMPING AS?

KJELL LOEN is the largest registered owner, with 100.0%.

What is the revenue of LO-VIK CAMPING AS?

LO-VIK CAMPING AS had revenue of NOK 3.2m in 2024.

Who is the general manager of LO-VIK CAMPING AS?

Kjell Loen is registered as general manager of LO-VIK CAMPING AS.

Where is LO-VIK CAMPING AS based?

LO-VIK CAMPING AS has its business address in Loen.

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.