BIZTRAC BETA
Restaurant activities

VAMOS TRYSIL AS

Org. no. 925378828 Limited company (AS) Trysil Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 17.6m
Operating profit NOK 1.7m
Equity NOK 151,000
Incorporated 2020
Employees 27
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-04-25 Adresseendring registrert 2026-04-25.

VAMOS TRYSIL AS is registered as a limited company in Trysil, Innlandet with organisation number 925378828. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 27 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av serveringssted og restaurant, samt investering i eiendom og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.6m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 17.6m
Operating profit
NOK 1.7m
Equity
NOK 151,000
Est. value
NOK 6.6m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.4%
Not satisfactory
Equity as a share of total capital

Who owns VAMOS TRYSIL AS?

MARIT GRØNDALEN ÖHLIN
VAMOS TRYSIL AS
NOK 17.6m rev. · NOK 1.7m profit

VAMOS TRYSIL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VAMOS TRYSIL AS

Who owns VAMOS TRYSIL AS?

MARIT GRØNDALEN ÖHLIN is the largest registered owner, with 66.0%.

What is the revenue of VAMOS TRYSIL AS?

VAMOS TRYSIL AS had revenue of NOK 17.6m in 2025.

Who is the general manager of VAMOS TRYSIL AS?

Marit Grøndalen Öhlin is registered as general manager of VAMOS TRYSIL AS.

Where is VAMOS TRYSIL AS based?

VAMOS TRYSIL 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.