BIZTRAC BETA
Marine fishing

STRAUMEN FISK AS

Org. no. 918777806 Limited company (AS) Lyngen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 12,000
Operating profit NOK −108,000
Equity NOK 5.5m
Incorporated 2017
Share capital NOK 52,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−108k kr).

STRAUMEN FISK AS is registered as a limited company in Lyngen, Troms with organisation number 918777806. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2017. Registered share capital is NOK 52,000, divided into 172700 shares. The company's stated purpose is: “Drive fiske og fangst av alle fiskeslag.”. The most recent filed accounts, for the 2024 financial year, show NOK 12,000 in revenue and NOK −108,000 in operating profit.

Key figures · 2024

Revenue
NOK 12,000
Operating profit
NOK −108,000
Equity
NOK 5.5m
Est. value
NOK 5.3m

Financial health · 2024

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
70.5%
Very good
Equity as a share of total capital

Who owns STRAUMEN FISK AS?

F. WIKERØY HOLDING AS
STRAUMEN FISK AS
NOK 12,000 rev. · NOK −108,000 profit

STRAUMEN FISK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STRAUMEN FISK AS own?

STRAUMEN FISK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STRAUMEN FISK AS

Who owns STRAUMEN FISK AS?

F. WIKERØY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STRAUMEN FISK AS?

STRAUMEN FISK AS had revenue of NOK 12,000 in 2024.

Who is the general manager of STRAUMEN FISK AS?

Frode Wikerøy is registered as general manager of STRAUMEN FISK AS.

Where is STRAUMEN FISK AS based?

STRAUMEN FISK AS has its business address in Nord-Lenangen.

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.