biztrac. BETA
COMPANY REGISTER PROFILE
998620767 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Travel agency activities

VIVI TRAVELS & TOURS AS

Org. no. 998620767 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 13.0m
Operating profit NOK 98,000
Equity NOK 669,000
Incorporated 2012
Share capital NOK 30,000

VIVI TRAVELS & TOURS AS is registered as a limited company in Oslo, Oslo with organisation number 998620767. The business is classified under travel agency activities (NACE 79.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive innen reiselivsbransjen (NACE-bransje 79.120 Reisearrangørvirksomhet), med reiselivsvirksomhet, herunder salg av flyreiser og pakkereiser.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.0m in revenue and NOK 98,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.0m
▲ +1 %
Operating profit
NOK 98,000
▼ −76 %
Equity
NOK 669,000
▲ +13 %
Est. value
NOK 944,000

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
9.9%
Satisfactory
Return on total assets
Solidity
58.4%
Very good
Equity as a share of total capital

Who owns VIVI TRAVELS & TOURS AS?

VIVI TRAVELS & TOURS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIVI TRAVELS & TOURS AS

Who owns VIVI TRAVELS & TOURS AS?

Arthi Vigneswaran is the largest registered owner, with 25.0%.

What is the revenue of VIVI TRAVELS & TOURS AS?

VIVI TRAVELS & TOURS AS had revenue of NOK 13.0m in 2025.

Who is the general manager of VIVI TRAVELS & TOURS AS?

Nirun Vigneswaran is registered as general manager of VIVI TRAVELS & TOURS AS.

Where is VIVI TRAVELS & TOURS AS based?

VIVI TRAVELS & TOURS AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.