BIZTRAC BETA
Camping grounds and recreational vehicle parks

LESJASKOGSVATNET CAMPING AS

Org. no. 990603219 Limited company (AS) Lesja Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 236,000
Equity NOK 1.4m
Incorporated 2006
Share capital NOK 450,000

LESJASKOGSVATNET CAMPING AS is registered as a limited company in Lesja, Innlandet with organisation number 990603219. 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 450,000, divided into 450 shares. The company's stated purpose is: “Campingplassvirksomhet, kiosksalg og kafè og annen virksomhet rettet inn mot turisme og fritidsaktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 236,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 236,000
Equity
NOK 1.4m
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.6%
Good
Equity as a share of total capital

Who owns LESJASKOGSVATNET CAMPING AS?

PER ODDVAR SÆTH
LESJASKOGSVATNET CAMPING AS
NOK 1.1m rev. · NOK 236,000 profit

LESJASKOGSVATNET CAMPING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LESJASKOGSVATNET CAMPING AS

Who owns LESJASKOGSVATNET CAMPING AS?

PER ODDVAR SÆTH is the largest registered owner, with 50.0%.

What is the revenue of LESJASKOGSVATNET CAMPING AS?

LESJASKOGSVATNET CAMPING AS had revenue of NOK 1.1m in 2025.

Who is the general manager of LESJASKOGSVATNET CAMPING AS?

Per Oddvar Sæth is registered as general manager of LESJASKOGSVATNET CAMPING AS.

Where is LESJASKOGSVATNET CAMPING AS based?

LESJASKOGSVATNET CAMPING AS has its business address in Lesjaskog.

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.