BIZTRAC BETA
Uoppgitt

STEVEFISK HOLDING AS

Org. no. 925755877 Limited company (AS) Tromsø Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −43,000
Equity NOK 23.8m
Incorporated 2020
Share capital NOK 30,000

Signals

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

STEVEFISK HOLDING AS is registered as a limited company in Tromsø, Troms with organisation number 925755877. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet med hovedvekt på direkte eller indirekte investeringer i aksjer og eiendom, samt virksomhet som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −43,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −43,000
Equity
NOK 23.8m
Est. value
NOK 14.6m

Financial health · 2024

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

Who owns STEVEFISK HOLDING AS?

CHRISTIAN GANGSTØ SETERLUND
STEVEFISK HOLDING AS
NOK 0 rev. · NOK −43,000 profit

STEVEFISK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STEVEFISK HOLDING AS own?

STEVEFISK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STEVEFISK HOLDING AS

Who owns STEVEFISK HOLDING AS?

CHRISTIAN GANGSTØ SETERLUND is the largest registered owner, with 100.0%.

What is the revenue of STEVEFISK HOLDING AS?

STEVEFISK HOLDING AS had revenue of NOK 0 in 2024.

Where is STEVEFISK HOLDING AS based?

STEVEFISK HOLDING AS has its business address in Tromsø.

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.