BIZTRAC BETA
Other tour operator activities

HOPALONG TRAVEL AS

Org. no. 993579181 Limited company (AS) Kåfjord Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 9.9m
Operating profit NOK −254,000
Equity NOK 334,000
Incorporated 2009
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−254k kr).
  • Nylig endring 2026-05-08 Adresseendring registrert 2026-05-08.

HOPALONG TRAVEL AS is registered as a limited company in Kåfjord, Troms with organisation number 993579181. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Å tilrettelegge og gjennomføre reisetilbud for nordmenn i USA.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.9m in revenue and NOK −254,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.9m
Operating profit
NOK −254,000
Equity
NOK 334,000
Est. value
NOK 5.9m

Financial health · 2024

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

Who owns HOPALONG TRAVEL AS?

KJETIL SVEISTRUP
HOPALONG TRAVEL AS
NOK 9.9m rev. · NOK −254,000 profit

HOPALONG TRAVEL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOPALONG TRAVEL AS

Who owns HOPALONG TRAVEL AS?

KJETIL SVEISTRUP is the largest registered owner, with 63.5%.

What is the revenue of HOPALONG TRAVEL AS?

HOPALONG TRAVEL AS had revenue of NOK 9.9m in 2024.

Who is the general manager of HOPALONG TRAVEL AS?

Kjetil Sveistrup is registered as general manager of HOPALONG TRAVEL AS.

Where is HOPALONG TRAVEL AS based?

HOPALONG TRAVEL AS has its business address in Birtavarre.

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.