BIZTRAC BETA
Other recreational activities

MAARFJELL AS

Org. no. 989453610 Limited company (AS) Tinn Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK −757,000
Equity NOK 1.8m
Incorporated 2006
Share capital NOK 100,000

Signals

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

MAARFJELL AS is registered as a limited company in Tinn, Telemark with organisation number 989453610. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1 shares. The company's stated purpose is: “Landbruksnæring med utleige av utmarksareal for jakt, fiske og opplevingar på Hardangervidda.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK −757,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK −757,000
Equity
NOK 1.8m
Est. value
NOK 3.4m

Financial health · 2024

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

Who owns MAARFJELL AS?

MAARFJELL SAMEIGE
MAARFJELL AS
NOK 2.6m rev. · NOK −757,000 profit

MAARFJELL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MAARFJELL AS own?

MAARFJELL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MAARFJELL AS

Who owns MAARFJELL AS?

MAARFJELL SAMEIGE is the largest registered owner, with 100.0%.

What is the revenue of MAARFJELL AS?

MAARFJELL AS had revenue of NOK 2.6m in 2025.

Who is the general manager of MAARFJELL AS?

Stein Olav Haakanes Rue is registered as general manager of MAARFJELL AS.

Where is MAARFJELL AS based?

MAARFJELL AS has its business address in Atrå.

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.