BIZTRAC BETA
Operation of sports facilities

MYRKDALEN FREESTYLEANLEGG AS

Org. no. 995263440 Limited company (AS) Voss Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 500,000
Operating profit NOK 233,000
Equity NOK 3.0m
Incorporated 2010
Share capital NOK 100,000

MYRKDALEN FREESTYLEANLEGG AS is registered as a limited company in Voss, Vestland with organisation number 995263440. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utbygging og tilrettelegging av anlegg for freestyleidretten samt legge til rette for trening og renn. Selskapet har ikkje økonomisk føremål for si verksemd og har følgjeleg ikkje som føremål å skaffe aksjonærane økonomisk utbytte.”. The most recent filed accounts, for the 2024 financial year, show NOK 500,000 in revenue and NOK 233,000 in operating profit.

Key figures · 2024

Revenue
NOK 500,000
Operating profit
NOK 233,000
Equity
NOK 3.0m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns MYRKDALEN FREESTYLEANLEGG AS?

NORWAY'S BEST AS
MYRKDALEN FREESTYLEANLEGG AS
NOK 500,000 rev. · NOK 233,000 profit

MYRKDALEN FREESTYLEANLEGG AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about MYRKDALEN FREESTYLEANLEGG AS

Who owns MYRKDALEN FREESTYLEANLEGG AS?

NORWAY'S BEST AS is the largest registered owner, with 44.0%.

What is the revenue of MYRKDALEN FREESTYLEANLEGG AS?

MYRKDALEN FREESTYLEANLEGG AS had revenue of NOK 500,000 in 2024.

Where is MYRKDALEN FREESTYLEANLEGG AS based?

MYRKDALEN FREESTYLEANLEGG 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.