BIZTRAC BETA
Support activities for fishing and aquaculture

SFS INVEST AS

Org. no. 919854189 Limited company (AS) Stavanger Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −30,000
Equity NOK −127,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

SFS INVEST AS is registered as a limited company in Stavanger, Rogaland with organisation number 919854189. The business is classified under support activities for fishing and aquaculture (NACE 03.300). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i verdipapirer samt deltakelse i andre selskapet av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK −127,000

Financial health · 2024

Liquidity
0.21
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-377.4%
Weak
Equity as a share of total capital

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

Who owns SFS INVEST AS?

FOGO AS
SFS INVEST AS
NOK 0 rev. · NOK −30,000 profit

SFS INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SFS INVEST AS own?

SFS INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SFS INVEST AS

Who owns SFS INVEST AS?

FOGO AS is the largest registered owner, with 96.0%.

What is the revenue of SFS INVEST AS?

SFS INVEST AS had revenue of NOK 0 in 2024.

Where is SFS INVEST AS based?

SFS INVEST AS has its business address in Stavanger.

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.