BIZTRAC BETA
Hotels and similar accommodation

WALAKER HOTELL AS

Org. no. 888241752 Limited company (AS) Luster Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 23.3m
Operating profit NOK 1.9m
Equity NOK 12.6m
Incorporated 2005
Employees 28
Share capital NOK 600,000

WALAKER HOTELL AS is registered as a limited company in Luster, Vestland with organisation number 888241752. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2005 and has 28 registered employees. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Hotel og anna verksemd som har samanheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.3m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 23.3m
Operating profit
NOK 1.9m
Equity
NOK 12.6m
Est. value
NOK 11.2m

Financial health · 2024

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

Who owns WALAKER HOTELL AS?

OLE-HENRIK NITTER WALAKER
WALAKER HOTELL AS
NOK 23.3m rev. · NOK 1.9m profit

WALAKER HOTELL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WALAKER HOTELL AS own?

WALAKER HOTELL AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about WALAKER HOTELL AS

Who owns WALAKER HOTELL AS?

OLE-HENRIK NITTER WALAKER is the largest registered owner, with 100.0%.

What is the revenue of WALAKER HOTELL AS?

WALAKER HOTELL AS had revenue of NOK 23.3m in 2024.

Who is the general manager of WALAKER HOTELL AS?

Ole-Henrik Nitter Walaker is registered as general manager of WALAKER HOTELL AS.

Where is WALAKER HOTELL AS based?

WALAKER HOTELL AS has its business address in Solvorn.

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.