BIZTRAC BETA
Restaurant activities

RESTAURANTHUSET FAGERÅSEN AS

Org. no. 922772436 Limited company (AS) Trysil Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 20.6m
Operating profit NOK 1.3m
Equity NOK 2.6m
Incorporated 2019
Employees 10
Share capital NOK 30,000

RESTAURANTHUSET FAGERÅSEN AS is registered as a limited company in Trysil, Innlandet with organisation number 922772436. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Selskapets virksomhet er restaurantvirksomhet, samt alt hva som her står i forbindelse med.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.6m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 20.6m
Operating profit
NOK 1.3m
Equity
NOK 2.6m
Est. value
NOK 6.4m

Financial health · 2025

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

Who owns RESTAURANTHUSET FAGERÅSEN AS?

MSNM HOLDING AB
RESTAURANTHUSET FAGERÅSEN AS
NOK 20.6m rev. · NOK 1.3m profit

RESTAURANTHUSET FAGERÅSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RESTAURANTHUSET FAGERÅSEN AS

Who owns RESTAURANTHUSET FAGERÅSEN AS?

MSNM HOLDING AB is the largest registered owner, with 100.0%.

What is the revenue of RESTAURANTHUSET FAGERÅSEN AS?

RESTAURANTHUSET FAGERÅSEN AS had revenue of NOK 20.6m in 2025.

Who is the general manager of RESTAURANTHUSET FAGERÅSEN AS?

Martin Sturmhoefel is registered as general manager of RESTAURANTHUSET FAGERÅSEN AS.

Where is RESTAURANTHUSET FAGERÅSEN AS based?

RESTAURANTHUSET FAGERÅSEN AS has its business address in Trysil.

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.