biztrac. BETA
COMPANY REGISTER PROFILE
935246539 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of adventure companies

TRAD ADVENTURES AS

Org. no. 935246539 Limited company (AS) Vågan Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 422,000
Operating profit NOK 146,000
Equity NOK 144,000
Incorporated 2025
Share capital NOK 30,000

TRAD ADVENTURES AS is registered as a limited company in Vågan, Nordland with organisation number 935246539. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilby aktiviteter og tjenester innen fjellklatring, friluftsliv, og naturbaserte opplevelser i Lofoten. Arrangere kurs, guidede turer og spesialtilpassede opplevelser for enkeltpersoner, grupper og hotellgjester. Fokus på bærekraft og sikkerhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 422,000 in revenue and NOK 146,000 in operating profit.

Key figures · 2025

Revenue
NOK 422,000
Operating profit
NOK 146,000
Equity
NOK 144,000
Est. value
NOK 510,000

Financial health · 2025

Liquidity
2.22
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
63.2%
Very good
Equity as a share of total capital

Who owns TRAD ADVENTURES AS?

TRAD ADVENTURES AS
NOK 422,000 rev. · NOK 146,000 profit

TRAD ADVENTURES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRAD ADVENTURES AS

Who owns TRAD ADVENTURES AS?

Javier Yllera Medina is the largest registered owner, with 50.0%.

What is the revenue of TRAD ADVENTURES AS?

TRAD ADVENTURES AS had revenue of NOK 422,000 in 2025.

Where is TRAD ADVENTURES AS based?

TRAD ADVENTURES AS has its business address in Henningsvær.

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.