BIZTRAC BETA
Hotels and similar accommodation

VÆRØY HOTELLDRIFT AS

Org. no. 835374262 Limited company (AS) Værøy Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 144,000
Equity NOK 137,000
Incorporated 2025
Share capital NOK 30,000

VÆRØY HOTELLDRIFT AS is registered as a limited company in Værøy, Nordland with organisation number 835374262. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen overnatting og matservering - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 144,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 144,000
Equity
NOK 137,000
Est. value
NOK 738,000

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.7%
Weak
Equity as a share of total capital

Who owns VÆRØY HOTELLDRIFT AS?

KJELL GUNNAR LINDZEN
VÆRØY HOTELLDRIFT AS
NOK 3.1m rev. · NOK 144,000 profit

VÆRØY HOTELLDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VÆRØY HOTELLDRIFT AS

Who owns VÆRØY HOTELLDRIFT AS?

KJELL GUNNAR LINDZEN is the largest registered owner, with 100.0%.

What is the revenue of VÆRØY HOTELLDRIFT AS?

VÆRØY HOTELLDRIFT AS had revenue of NOK 3.1m in 2025.

Who is the general manager of VÆRØY HOTELLDRIFT AS?

Kjell Gunnar Lindzen is registered as general manager of VÆRØY HOTELLDRIFT AS.

Where is VÆRØY HOTELLDRIFT AS based?

VÆRØY HOTELLDRIFT AS has its business address in Værøy.

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.