biztrac. BETA
COMPANY REGISTER PROFILE
985058733 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Other tour operator activities

ASKELADDEN REISER AS

Org. no. 985058733 Limited company (AS) Ringerike Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 115,000
Equity NOK 183,000
Incorporated 2002
Share capital NOK 859,000

ASKELADDEN REISER AS is registered as a limited company in Ringerike, Buskerud with organisation number 985058733. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2002. Registered share capital is NOK 859,000, divided into 85860 shares. The company's stated purpose is: “Reisearrangør og dertil hørende aktiviteter som faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 115,000 in operating profit.

Former names: VIKING TOURS AS

Key figures · 2025

Revenue
NOK 4.6m
▼ −18 %
Operating profit
NOK 115,000
▼ −14 %
Equity
NOK 183,000
▼ −68 %
Est. value
NOK 633,000

Financial health · 2025

Liquidity
2.11
Very good
Current assets ÷ current liabilities
Profitability
22.1%
Very good
Return on total assets
Solidity
52.7%
Very good
Equity as a share of total capital

Who owns ASKELADDEN REISER AS?

ASKELADDEN REISER AS
NOK 4.6m rev. · NOK 115,000 profit

ASKELADDEN REISER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASKELADDEN REISER AS

Who owns ASKELADDEN REISER AS?

Rolf Lie is the largest registered owner, with 100.0%.

What is the revenue of ASKELADDEN REISER AS?

ASKELADDEN REISER AS had revenue of NOK 4.6m in 2025.

Who is the general manager of ASKELADDEN REISER AS?

Rolf Lie is registered as general manager of ASKELADDEN REISER AS.

Where is ASKELADDEN REISER AS based?

ASKELADDEN REISER AS has its business address in Hønefoss.

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.