BIZTRAC BETA
Holiday and other short-stay accommodation

ENJOY LOFOTEN AS

Org. no. 918525637 Limited company (AS) Harstad Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 724,000
Operating profit NOK 27,000
Equity NOK 175,000
Incorporated 2017
Share capital NOK 100,000

ENJOY LOFOTEN AS is registered as a limited company in Harstad, Troms with organisation number 918525637. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av fritidsbolig, matopplevelse og salg av mat, samt investere i sammenfallende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 724,000 in revenue and NOK 27,000 in operating profit.

Key figures · 2024

Revenue
NOK 724,000
Operating profit
NOK 27,000
Equity
NOK 175,000
Est. value
NOK 155,000

Financial health · 2024

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.3%
Weak
Equity as a share of total capital

Who owns ENJOY LOFOTEN AS?

RONNY SØRENSEN
ENJOY LOFOTEN AS
NOK 724,000 rev. · NOK 27,000 profit

ENJOY LOFOTEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ENJOY LOFOTEN AS own?

ENJOY LOFOTEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ENJOY LOFOTEN AS

Who owns ENJOY LOFOTEN AS?

RONNY SØRENSEN is the largest registered owner, with 50.0%.

What is the revenue of ENJOY LOFOTEN AS?

ENJOY LOFOTEN AS had revenue of NOK 724,000 in 2024.

Who is the general manager of ENJOY LOFOTEN AS?

Viggo Svanstrøm is registered as general manager of ENJOY LOFOTEN AS.

Where is ENJOY LOFOTEN AS based?

ENJOY LOFOTEN AS has its business address in Harstad.

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.