biztrac. BETA
COMPANY REGISTER PROFILE
929371453 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of tour guides

RIDENOWTRAVELS AS

Org. no. 929371453 Limited company (AS) Vestvågøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 176,000
Operating profit NOK 44,000
Equity NOK −88,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−88k kr).
  • Nylig endring 2026-05-31 Adresseendring registrert 2026-05-31.

RIDENOWTRAVELS AS is registered as a limited company in Vestvågøy, Nordland with organisation number 929371453. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Turistvirksomhet, guidetjenester, fotografering.”. The most recent filed accounts, for the 2025 financial year, show NOK 176,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 176,000
▲ +477 %
Operating profit
NOK 44,000
▲ +149 %
Equity
NOK −88,000
▲ +27 %

Financial health · 2025

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
70.7%
Very good
Return on total assets
Solidity
-69.8%
Weak
Equity as a share of total capital

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

Who owns RIDENOWTRAVELS AS?

RIDENOWTRAVELS AS
NOK 176,000 rev. · NOK 44,000 profit

RIDENOWTRAVELS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RIDENOWTRAVELS AS

Who owns RIDENOWTRAVELS AS?

Cyril Adamek is the largest registered owner, with 100.0%.

What is the revenue of RIDENOWTRAVELS AS?

RIDENOWTRAVELS AS had revenue of NOK 176,000 in 2025.

Where is RIDENOWTRAVELS AS based?

RIDENOWTRAVELS AS has its business address in Bøstad.

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.