BIZTRAC BETA
Activities of tour guides

LEGENDARY ARCTIC AS

Org. no. 935080142 Limited company (AS) Tromsø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 523,000
Operating profit NOK 24,000
Equity NOK 44,000
Incorporated 2025
Share capital NOK 30,000

LEGENDARY ARCTIC AS is registered as a limited company in Tromsø, Troms with organisation number 935080142. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilby guide- og reiseledertjenester, herunder, men ikke begrenset til, omvisninger, turplanlegging, koordinering av reiseaktiviteter og formidling av informasjon om lokale attraksjoner, historie og kultur.”. The most recent filed accounts, for the 2025 financial year, show NOK 523,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 523,000
Operating profit
NOK 24,000
Equity
NOK 44,000
Est. value
NOK 123,000

Financial health · 2025

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

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

Who owns LEGENDARY ARCTIC AS?

LEGENDARY GROUP AS
LEGENDARY ARCTIC AS
NOK 523,000 rev. · NOK 24,000 profit

LEGENDARY ARCTIC AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LEGENDARY ARCTIC AS er morselskap for 2 datterselskaper:

Frequently asked questions about LEGENDARY ARCTIC AS

Who owns LEGENDARY ARCTIC AS?

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

What is the revenue of LEGENDARY ARCTIC AS?

LEGENDARY ARCTIC AS had revenue of NOK 523,000 in 2025.

Where is LEGENDARY ARCTIC AS based?

LEGENDARY ARCTIC AS has its business address in Tromsø.

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.