BIZTRAC BETA
Holiday and other short-stay accommodation

NARVIK ADVENTURES AS

Org. no. 919711116 Limited company (AS) Narvik Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −27,000
Equity NOK −33,000
Incorporated 2017
Employees 7
Share capital NOK 200,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−33k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−27k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NARVIK ADVENTURES AS is registered as a limited company in Narvik, Nordland with organisation number 919711116. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2017 and has 7 registered employees. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Overnatting, opplevelser, cafedrift og alt som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −27,000
Equity
NOK −33,000

Financial health · 2024

Liquidity
0.65
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-574.2%
Weak
Equity as a share of total capital

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

Who owns NARVIK ADVENTURES AS?

BEISFJORDGUBBEN AS
NARVIK ADVENTURES AS
· NOK −27,000 profit

NARVIK ADVENTURES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NARVIK ADVENTURES AS

Who owns NARVIK ADVENTURES AS?

BEISFJORDGUBBEN AS is the largest registered owner, with 100.0%.

Who is the general manager of NARVIK ADVENTURES AS?

Eilert Andre Ravn is registered as general manager of NARVIK ADVENTURES AS.

Where is NARVIK ADVENTURES AS based?

NARVIK ADVENTURES AS has its business address in Ballangen.

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.