BIZTRAC BETA
Hotels and similar accommodation

JUVASSHYTTA AS

Org. no. 990029946 Limited company (AS) Lom Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 16.8m
Operating profit NOK 2.2m
Equity NOK 8.4m
Incorporated 2006
Employees 8
Share capital NOK 100,000

JUVASSHYTTA AS is registered as a limited company in Lom, Innlandet with organisation number 990029946. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2006 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive virksomhet innen reiseliv med overnatting, servering og annen virksomhet forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.8m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 16.8m
Operating profit
NOK 2.2m
Equity
NOK 8.4m
Est. value
NOK 13.4m

Financial health · 2025

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

Who owns JUVASSHYTTA AS?

JUVASSHYTTA HOLDING AS
JUVASSHYTTA AS
NOK 16.8m rev. · NOK 2.2m profit

JUVASSHYTTA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JUVASSHYTTA AS own?

JUVASSHYTTA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JUVASSHYTTA AS

Who owns JUVASSHYTTA AS?

JUVASSHYTTA HOLDING AS is the largest registered owner, with 96.0%.

What is the revenue of JUVASSHYTTA AS?

JUVASSHYTTA AS had revenue of NOK 16.8m in 2025.

Who is the general manager of JUVASSHYTTA AS?

Silje Stee Vole is registered as general manager of JUVASSHYTTA AS.

Where is JUVASSHYTTA AS based?

JUVASSHYTTA AS has its business address in Bøverdalen.

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.