BIZTRAC BETA
COMPANY REGISTER PROFILE
919326239 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 02.09.2026
Marine fishing

FONN FISK AS

Org. no. 919326239 Limited company (AS) Kvæfjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 38,000
Operating profit NOK −173,000
Equity NOK −61,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−61k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−173k kr).

FONN FISK AS is registered as a limited company in Kvæfjord, Troms with organisation number 919326239. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fiske, men også eiendomsdrift og utleie av arbeidskraft og utstyr, samt utførelse av håndverktjenester og annet praktisk arbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 38,000 in revenue and NOK −173,000 in operating profit.

Key figures · 2025

Revenue
NOK 38,000
▲ +459 %
Operating profit
NOK −173,000
▲ +15 %
Equity
NOK −61,000
▼ −181 %

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
-47.6%
Not satisfactory
Return on total assets
Solidity
-14.5%
Weak
Equity as a share of total capital

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

Who owns FONN FISK AS?

FONN FISK AS
NOK 38,000 rev. · NOK −173,000 profit

FONN FISK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FONN FISK AS

Who owns FONN FISK AS?

VIDAR FONN is the largest registered owner, with 51.0%.

What is the revenue of FONN FISK AS?

FONN FISK AS had revenue of NOK 38,000 in 2025.

Where is FONN FISK AS based?

FONN FISK AS has its business address in Borkenes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.