BIZTRAC BETA
Other tour operator activities

EXPLORE SRI LANKA AS

Org. no. 924918632 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 954,000
Operating profit NOK 14,000
Equity NOK 17,000
Incorporated 2020
Share capital NOK 30,000

EXPLORE SRI LANKA AS is registered as a limited company in Oslo, Oslo with organisation number 924918632. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Reiseformidling, investeringer og lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 954,000 in revenue and NOK 14,000 in operating profit.

Key figures · 2025

Revenue
NOK 954,000
Operating profit
NOK 14,000
Equity
NOK 17,000
Est. value
NOK 82,000

Financial health · 2025

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

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

Who owns EXPLORE SRI LANKA AS?

ROSHAN PRASANGA DAYANANDA KAHANDA KARUNARATNAGE
EXPLORE SRI LANKA AS
NOK 954,000 rev. · NOK 14,000 profit

EXPLORE SRI LANKA AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about EXPLORE SRI LANKA AS

Who owns EXPLORE SRI LANKA AS?

ROSHAN PRASANGA DAYANANDA KAHANDA KARUNARATNAGE is the largest registered owner, with 40.0%.

What is the revenue of EXPLORE SRI LANKA AS?

EXPLORE SRI LANKA AS had revenue of NOK 954,000 in 2025.

Who is the general manager of EXPLORE SRI LANKA AS?

Roshan Prasanga Dayananda Kahanda Karunaratnage is registered as general manager of EXPLORE SRI LANKA AS.

Where is EXPLORE SRI LANKA AS based?

EXPLORE SRI LANKA 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.