BIZTRAC BETA
Other tour operator activities

TRAVEL INVEST AS

Org. no. 988560774 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −190,000
Equity NOK 17.8m
Incorporated 2005
Share capital NOK 10.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−190k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TRAVEL INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 988560774. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2005. Registered share capital is NOK 10.0m, divided into 10000 shares. The company's stated purpose is: “Investeringer innenfor reiselivsbransjen, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med liknende virksomhet.”.

Key figures · 2024

Operating profit
NOK −190,000
Equity
NOK 17.8m
Est. value
NOK 360.0m

Financial health · 2024

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.8%
Good
Equity as a share of total capital

Who owns TRAVEL INVEST AS?

ARMADA AS
TRAVEL INVEST AS
· NOK −190,000 profit

TRAVEL INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does TRAVEL INVEST AS own?

TRAVEL INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

TRAVEL INVEST AS er morselskap for 2 datterselskaper:

Frequently asked questions about TRAVEL INVEST AS

Who owns TRAVEL INVEST AS?

ARMADA AS is the largest registered owner, with 40.0%.

Who is the general manager of TRAVEL INVEST AS?

Arthur Kordt is registered as general manager of TRAVEL INVEST AS.

Where is TRAVEL INVEST AS based?

TRAVEL INVEST AS has its business address in Bergen.

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.