BIZTRAC BETA
Marine fishing

BOKN FISK OG FANGST AS

Org. no. 818776462 Limited company (AS) Bokn Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −2.0m
Equity NOK 1.3m
Incorporated 2017
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,0 mill kr).

BOKN FISK OG FANGST AS is registered as a limited company in Bokn, Rogaland with organisation number 818776462. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2017. Registered share capital is NOK 50,000, divided into 5000 shares. The company's stated purpose is: “Drive med fiskeri med garn og teiner langs kysten, samt hva hermed står i forbindelse, herunder å delta i andre foretak med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −2.0m in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK −2.0m
Equity
NOK 1.3m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns BOKN FISK OG FANGST AS?

ERIK ALVESTAD
BOKN FISK OG FANGST AS
NOK 1.6m rev. · NOK −2.0m profit

BOKN FISK OG FANGST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BOKN FISK OG FANGST AS own?

BOKN FISK OG FANGST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BOKN FISK OG FANGST AS

Who owns BOKN FISK OG FANGST AS?

ERIK ALVESTAD is the largest registered owner, with 66.0%.

What is the revenue of BOKN FISK OG FANGST AS?

BOKN FISK OG FANGST AS had revenue of NOK 1.6m in 2025.

Where is BOKN FISK OG FANGST AS based?

BOKN FISK OG FANGST AS has its business address in Bokn.

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.