BIZTRAC BETA
Other tour operator activities

ESCAPE TRAVEL AS

Org. no. 966681454 Limited company (AS) Oslo Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 504.5m
Operating profit NOK 11.1m
Equity NOK 37.1m
Incorporated 1993
Employees 55
Share capital NOK 3.8m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ESCAPE TRAVEL AS is registered as a limited company in Oslo, Oslo with organisation number 966681454. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 1993 and has 55 registered employees. Registered share capital is NOK 3.8m, divided into 7600 shares. The company's stated purpose is: “Reisevirksomhet samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 504.5m in revenue and NOK 11.1m in operating profit.

Key figures · 2025

Revenue
NOK 504.5m
Operating profit
NOK 11.1m
Equity
NOK 37.1m
Est. value
NOK 65.6m

Financial health · 2025

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

Who owns ESCAPE TRAVEL AS?

ESCAPE TRAVEL GROUP AS
ESCAPE TRAVEL AS
NOK 504.5m rev. · NOK 11.1m profit

ESCAPE TRAVEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESCAPE TRAVEL AS

Who owns ESCAPE TRAVEL AS?

ESCAPE TRAVEL GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of ESCAPE TRAVEL AS?

ESCAPE TRAVEL AS had revenue of NOK 504.5m in 2025.

Who is the general manager of ESCAPE TRAVEL AS?

Tor Johan Pedersen is registered as general manager of ESCAPE TRAVEL AS.

Where is ESCAPE TRAVEL AS based?

ESCAPE TRAVEL 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 15.06.2026.

Report a problem

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