BIZTRAC BETA
Hotels and similar accommodation

ORKELBOGEN FRILUFTSENTER AS

Org. no. 919282878 Limited company (AS) Tynset Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK −735,000
Equity NOK 529,000
Incorporated 2017
Employees 9
Share capital NOK 2.6m

Signals

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

ORKELBOGEN FRILUFTSENTER AS is registered as a limited company in Tynset, Innlandet with organisation number 919282878. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2017 and has 9 registered employees. Registered share capital is NOK 2.6m, divided into 260 shares. The company's stated purpose is: “Drift av kurssenter, romutleie, konferansedrift, serveringsvirksomhet samt virksomhet som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK −735,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK −735,000
Equity
NOK 529,000
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns ORKELBOGEN FRILUFTSENTER AS?

S. MUNKHAUGEN AS
ORKELBOGEN FRILUFTSENTER AS
NOK 2.3m rev. · NOK −735,000 profit

ORKELBOGEN FRILUFTSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORKELBOGEN FRILUFTSENTER AS

Who owns ORKELBOGEN FRILUFTSENTER AS?

S. MUNKHAUGEN AS is the largest registered owner, with 100.0%.

What is the revenue of ORKELBOGEN FRILUFTSENTER AS?

ORKELBOGEN FRILUFTSENTER AS had revenue of NOK 2.3m in 2025.

Where is ORKELBOGEN FRILUFTSENTER AS based?

ORKELBOGEN FRILUFTSENTER AS has its business address in Kvikne.

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.