BIZTRAC BETA
Hotels and similar accommodation

RØISHEIM HOTELL AS

Org. no. 989976036 Limited company (AS) Lom Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 10.1m
Operating profit NOK 1.3m
Equity NOK 1.4m
Incorporated 2006
Employees 5
Share capital NOK 200,000

RØISHEIM HOTELL AS is registered as a limited company in Lom, Innlandet with organisation number 989976036. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2006 and has 5 registered employees. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Selskapets virksomhet er drift av hoteller, pensjonater og moteller med restaurant.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.1m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 10.1m
Operating profit
NOK 1.3m
Equity
NOK 1.4m
Est. value
NOK 5.4m

Financial health · 2025

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.8%
Good
Equity as a share of total capital

Who owns RØISHEIM HOTELL AS?

RØISHEIM EIENDOM AS
RØISHEIM HOTELL AS
NOK 10.1m rev. · NOK 1.3m profit

RØISHEIM HOTELL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RØISHEIM HOTELL AS own?

RØISHEIM HOTELL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RØISHEIM HOTELL AS

Who owns RØISHEIM HOTELL AS?

RØISHEIM EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of RØISHEIM HOTELL AS?

RØISHEIM HOTELL AS had revenue of NOK 10.1m in 2025.

Who is the general manager of RØISHEIM HOTELL AS?

Maja Hyldal Sørensen is registered as general manager of RØISHEIM HOTELL AS.

Where is RØISHEIM HOTELL AS based?

RØISHEIM HOTELL AS has its business address in Lom.

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.