BIZTRAC BETA
Activities of adventure companies

VESTERÅLEN FISHING AS

Org. no. 915313728 Limited company (AS) Øksnes Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 252,000
Equity NOK 419,000
Incorporated 2015
Share capital NOK 3.0m

VESTERÅLEN FISHING AS is registered as a limited company in Øksnes, Nordland with organisation number 915313728. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2015. Registered share capital is NOK 3.0m, divided into 100 shares. The company's stated purpose is: “Fisketurisme, utleie av hytte og båter, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 252,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 252,000
Equity
NOK 419,000
Est. value
NOK 830,000

Financial health · 2024

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

Who owns VESTERÅLEN FISHING AS?

EDGARD MATTY G STIJVEN
VESTERÅLEN FISHING AS
NOK 1.1m rev. · NOK 252,000 profit

VESTERÅLEN FISHING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VESTERÅLEN FISHING AS

Who owns VESTERÅLEN FISHING AS?

EDGARD MATTY G STIJVEN is the largest registered owner, with 50.0%.

What is the revenue of VESTERÅLEN FISHING AS?

VESTERÅLEN FISHING AS had revenue of NOK 1.1m in 2024.

Who is the general manager of VESTERÅLEN FISHING AS?

Dave Josephine J Telen is registered as general manager of VESTERÅLEN FISHING AS.

Where is VESTERÅLEN FISHING AS based?

VESTERÅLEN FISHING AS has its business address in Myre.

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.