BIZTRAC BETA
Other tour operator activities

TRAVELEVENT AS

Org. no. 989982079 Limited company (AS) Time Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 55.8m
Operating profit NOK 1.9m
Equity NOK 3.3m
Incorporated 2006
Share capital NOK 300,000

TRAVELEVENT AS is registered as a limited company in Time, Rogaland with organisation number 989982079. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2006. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Formidling og arrangering av firmaturer, gruppereiser, opplevelser og annen virksomhet som naturlig faller under dette, samt å delta som aksjonær, eller delta på annen måte, ved investering i andre foretak. Salg av reklameartikler, firmaprofilering, arbeidstøy og detaljhandel med sport- og fritidsklær.”. The most recent filed accounts, for the 2024 financial year, show NOK 55.8m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 55.8m
Operating profit
NOK 1.9m
Equity
NOK 3.3m
Est. value
NOK 9.7m

Financial health · 2024

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.8%
Good
Equity as a share of total capital

Who owns TRAVELEVENT AS?

AEVENT AS
TRAVELEVENT AS
NOK 55.8m rev. · NOK 1.9m profit

TRAVELEVENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRAVELEVENT AS

Who owns TRAVELEVENT AS?

AEVENT AS is the largest registered owner, with 100.0%.

What is the revenue of TRAVELEVENT AS?

TRAVELEVENT AS had revenue of NOK 55.8m in 2024.

Who is the general manager of TRAVELEVENT AS?

Arild Torarin Otto is registered as general manager of TRAVELEVENT AS.

Where is TRAVELEVENT AS based?

TRAVELEVENT AS has its business address in Bryne.

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.