BIZTRAC BETA
Hotels and similar accommodation

HATTVIKA LODGE AS

Org. no. 920969224 Limited company (AS) Vestvågøy Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 31.8m
Operating profit NOK 1.3m
Equity NOK 4.8m
Incorporated 2018
Employees 19
Share capital NOK 134,000

HATTVIKA LODGE AS is registered as a limited company in Vestvågøy, Nordland with organisation number 920969224. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2018 and has 19 registered employees. Registered share capital is NOK 134,000, divided into 134 shares. The company's stated purpose is: “Drift av turistanlegg med tilhørende aktiviteter og arrangementer.”. The most recent filed accounts, for the 2025 financial year, show NOK 31.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 31.8m
Operating profit
NOK 1.3m
Equity
NOK 4.8m
Est. value
NOK 6.9m

Financial health · 2025

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

Who owns HATTVIKA LODGE AS?

KRISTIAN MAGNUS BØE
HATTVIKA LODGE AS
NOK 31.8m rev. · NOK 1.3m profit

HATTVIKA LODGE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HATTVIKA LODGE AS own?

HATTVIKA LODGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HATTVIKA LODGE AS

Who owns HATTVIKA LODGE AS?

KRISTIAN MAGNUS BØE is the largest registered owner, with 74.6%.

What is the revenue of HATTVIKA LODGE AS?

HATTVIKA LODGE AS had revenue of NOK 31.8m in 2025.

Who is the general manager of HATTVIKA LODGE AS?

Kristian Magnus Bøe is registered as general manager of HATTVIKA LODGE AS.

Where is HATTVIKA LODGE AS based?

HATTVIKA LODGE AS has its business address in Ballstad.

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.