BIZTRAC BETA
Camping grounds and recreational vehicle parks

MYRKDALEN CAMPING AS

Org. no. 916698771 Limited company (AS) Voss Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK −101,000
Equity NOK 297,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−101k kr).

MYRKDALEN CAMPING AS is registered as a limited company in Voss, Vestland with organisation number 916698771. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Driva campingplass samt anna verksemd som naturleg fell under denne forretningsverksemda.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK −101,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK −101,000
Equity
NOK 297,000
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns MYRKDALEN CAMPING AS?

BJØRG EEN KVALFOSS
MYRKDALEN CAMPING AS
NOK 2.0m rev. · NOK −101,000 profit

MYRKDALEN CAMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MYRKDALEN CAMPING AS

Who owns MYRKDALEN CAMPING AS?

BJØRG EEN KVALFOSS is the largest registered owner, with 100.0%.

What is the revenue of MYRKDALEN CAMPING AS?

MYRKDALEN CAMPING AS had revenue of NOK 2.0m in 2025.

Who is the general manager of MYRKDALEN CAMPING AS?

Bjørg Een Kvalfoss is registered as general manager of MYRKDALEN CAMPING AS.

Where is MYRKDALEN CAMPING AS based?

MYRKDALEN CAMPING AS has its business address in Vossestrand.

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.