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

EIK TRAVEL AS

Org. no. 992296119 Limited company (AS) Ringerike Incorporated 2008 Active
Revenue 2025 NOK 2.6m
Operating profit NOK −565,000
Equity NOK 3.5m
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−565k kr).

EIK TRAVEL AS is registered as a limited company in Ringerike, Buskerud with organisation number 992296119. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Arrangement av turer og hva derved er forbundet, samt deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK −565,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
▼ −83 %
Operating profit
NOK −565,000
▼ −136 %
Equity
NOK 3.5m
▼ −13 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
5.19
Very good
Current assets ÷ current liabilities
Profitability
-9.1%
Not satisfactory
Return on total assets
Solidity
80.7%
Very good
Equity as a share of total capital

Who owns EIK TRAVEL AS?

EIK TRAVEL AS
NOK 2.6m rev. · NOK −565,000 profit

EIK TRAVEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIK TRAVEL AS

Who owns EIK TRAVEL AS?

OLONANA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of EIK TRAVEL AS?

EIK TRAVEL AS had revenue of NOK 2.6m in 2025.

Who is the general manager of EIK TRAVEL AS?

Kjetil Eriksen is registered as general manager of EIK TRAVEL AS.

Where is EIK TRAVEL AS based?

EIK TRAVEL 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.