BIZTRAC BETA
Camping grounds and recreational vehicle parks

LYNGVÆR LOFOTEN BOBILCAMPING AS

Org. no. 922845484 Limited company (AS) Vågan Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 112,000
Equity NOK 2.4m
Incorporated 2019
Share capital NOK 480,000

LYNGVÆR LOFOTEN BOBILCAMPING AS is registered as a limited company in Vågan, Nordland with organisation number 922845484. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2019. Registered share capital is NOK 480,000, divided into 480 shares. The company's stated purpose is: “Drift av campingplass samt annet som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 112,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 112,000
Equity
NOK 2.4m
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.7%
Good
Equity as a share of total capital

Who owns LYNGVÆR LOFOTEN BOBILCAMPING AS?

LOFOTEN CAMPING AS
LYNGVÆR LOFOTEN BOBILCAMPING AS
NOK 2.9m rev. · NOK 112,000 profit

LYNGVÆR LOFOTEN BOBILCAMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYNGVÆR LOFOTEN BOBILCAMPING AS

Who owns LYNGVÆR LOFOTEN BOBILCAMPING AS?

LOFOTEN CAMPING AS is the largest registered owner, with 100.0%.

What is the revenue of LYNGVÆR LOFOTEN BOBILCAMPING AS?

LYNGVÆR LOFOTEN BOBILCAMPING AS had revenue of NOK 2.9m in 2025.

Who is the general manager of LYNGVÆR LOFOTEN BOBILCAMPING AS?

Kåre Andreas Rønning is registered as general manager of LYNGVÆR LOFOTEN BOBILCAMPING AS.

Where is LYNGVÆR LOFOTEN BOBILCAMPING AS based?

LYNGVÆR LOFOTEN BOBILCAMPING AS has its business address in Kleppstad.

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.