BIZTRAC BETA
Other tour operator activities

EXPA TRAVEL NORDIC AS

Org. no. 923835164 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 83,000
Operating profit NOK −153,000
Equity NOK 563,000
Incorporated 2019
Share capital NOK 201,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−153k kr).

EXPA TRAVEL NORDIC AS is registered as a limited company in Asker, Akershus with organisation number 923835164. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2019. Registered share capital is NOK 201,000, divided into 200600 shares. The company's stated purpose is: “Å utvikle, produsere, selge og tilby aktive reiser i inn- og utland.”. The most recent filed accounts, for the 2024 financial year, show NOK 83,000 in revenue and NOK −153,000 in operating profit.

Key figures · 2024

Revenue
NOK 83,000
Operating profit
NOK −153,000
Equity
NOK 563,000
Est. value
NOK 336,000

Financial health · 2024

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

Who owns EXPA TRAVEL NORDIC AS?

EXPA HOLDING AS
EXPA TRAVEL NORDIC AS
NOK 83,000 rev. · NOK −153,000 profit

EXPA TRAVEL NORDIC AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EXPA TRAVEL NORDIC AS own?

EXPA TRAVEL NORDIC AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EXPA TRAVEL NORDIC AS

Who owns EXPA TRAVEL NORDIC AS?

EXPA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of EXPA TRAVEL NORDIC AS?

EXPA TRAVEL NORDIC AS had revenue of NOK 83,000 in 2024.

Where is EXPA TRAVEL NORDIC AS based?

EXPA TRAVEL NORDIC AS has its business address in Hyggen.

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.