BIZTRAC BETA
Other tour operator activities

VOLLAN TRAVEL AS

Org. no. 995849879 Limited company (AS) Porsgrunn Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 165,000
Operating profit NOK −22,000
Equity NOK 62,000
Incorporated 2010
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

VOLLAN TRAVEL AS is registered as a limited company in Porsgrunn, Telemark with organisation number 995849879. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive reiseselskap, samt investeringer i aksjer og deltagelse i andre selskaper og verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 165,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 165,000
Operating profit
NOK −22,000
Equity
NOK 62,000
Est. value
NOK 136,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VOLLAN TRAVEL AS?

PER VOLLAN
VOLLAN TRAVEL AS
NOK 165,000 rev. · NOK −22,000 profit

VOLLAN TRAVEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOLLAN TRAVEL AS

Who owns VOLLAN TRAVEL AS?

PER VOLLAN is the largest registered owner, with 100.0%.

What is the revenue of VOLLAN TRAVEL AS?

VOLLAN TRAVEL AS had revenue of NOK 165,000 in 2025.

Who is the general manager of VOLLAN TRAVEL AS?

Per Vollan is registered as general manager of VOLLAN TRAVEL AS.

Where is VOLLAN TRAVEL AS based?

VOLLAN TRAVEL AS has its business address in Porsgrunn.

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.