BIZTRAC BETA
Activities of tour guides

MAGIC RIVER TRAVELS AS

Org. no. 920829910 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2023 NOK 3.3m
Operating profit NOK −30,000
Equity NOK 153,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−30k kr).
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.

MAGIC RIVER TRAVELS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920829910. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av fiskeopplevelser med guiding (turistfiske) og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2023 financial year, show NOK 3.3m in revenue and NOK −30,000 in operating profit.

Key figures · 2023

Revenue
NOK 3.3m
Operating profit
NOK −30,000
Equity
NOK 153,000
Est. value
NOK 2.2m

Financial health · 2023

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

Who owns MAGIC RIVER TRAVELS AS?

No shareholders are registered for MAGIC RIVER TRAVELS AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MAGIC RIVER TRAVELS AS

What is the revenue of MAGIC RIVER TRAVELS AS?

MAGIC RIVER TRAVELS AS had revenue of NOK 3.3m in 2023.

Who is the general manager of MAGIC RIVER TRAVELS AS?

William Sebastian Moberg Faulds is registered as general manager of MAGIC RIVER TRAVELS AS.

Where is MAGIC RIVER TRAVELS AS based?

MAGIC RIVER TRAVELS AS has its business address in Tiller.

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.