BIZTRAC BETA
Marine fishing

THORALF FISK AS

Org. no. 830177272 Limited company (AS) Nordkapp Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 693,000
Operating profit NOK −248,000
Equity NOK −323,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−323k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−248k kr).

THORALF FISK AS is registered as a limited company in Nordkapp, Finnmark with organisation number 830177272. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive fiske med eget fartøy samt det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 693,000 in revenue and NOK −248,000 in operating profit.

Key figures · 2024

Revenue
NOK 693,000
Operating profit
NOK −248,000
Equity
NOK −323,000

Financial health · 2024

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

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

Who owns THORALF FISK AS?

THORALF HANSEN
THORALF FISK AS
NOK 693,000 rev. · NOK −248,000 profit

THORALF FISK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about THORALF FISK AS

Who owns THORALF FISK AS?

THORALF HANSEN is the largest registered owner, with 100.0%.

What is the revenue of THORALF FISK AS?

THORALF FISK AS had revenue of NOK 693,000 in 2024.

Who is the general manager of THORALF FISK AS?

Thoralf Hansen is registered as general manager of THORALF FISK AS.

Where is THORALF FISK AS based?

THORALF FISK AS has its business address in Skarsvåg.

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.