BIZTRAC BETA
Holiday and other short-stay accommodation

VACATION TRYSIL AS

Org. no. 934304454 Limited company (AS) Trysil Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 195,000
Operating profit NOK −141,000
Equity NOK −117,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−117k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−141k kr).

VACATION TRYSIL AS is registered as a limited company in Trysil, Innlandet with organisation number 934304454. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive med utleie av feriebolig/leiligheter og annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 195,000 in revenue and NOK −141,000 in operating profit.

Key figures · 2025

Revenue
NOK 195,000
Operating profit
NOK −141,000
Equity
NOK −117,000

Financial health · 2025

Liquidity
0.56
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-77.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VACATION TRYSIL AS?

GEBAUER HOLDING AB, SELSKAP
VACATION TRYSIL AS
NOK 195,000 rev. · NOK −141,000 profit

VACATION TRYSIL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VACATION TRYSIL AS

Who owns VACATION TRYSIL AS?

GEBAUER HOLDING AB, SELSKAP is the largest registered owner, with 50.0%.

What is the revenue of VACATION TRYSIL AS?

VACATION TRYSIL AS had revenue of NOK 195,000 in 2025.

Where is VACATION TRYSIL AS based?

VACATION 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.