BIZTRAC BETA
Freight ocean transport

STENERSEN SHIPSINVEST AS

Org. no. 979699093 Limited company (AS) Bergen Incorporated 1998 Active
Ownership graph ↗
Operating profit NOK −126,000
Equity NOK 364.7m
Incorporated 1998
Share capital NOK 43.8m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−126k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STENERSEN SHIPSINVEST AS is registered as a limited company in Bergen, Vestland with organisation number 979699093. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 1998. Registered share capital is NOK 43.8m, divided into 55553 shares. The company's stated purpose is: “Delta i skipsfartsvirksomhet samt finansiering og investering i tilknytning til dette.”.

Key figures · 2024

Operating profit
NOK −126,000
Equity
NOK 364.7m
Est. value
NOK 788.9m

Financial health · 2024

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

Who owns STENERSEN SHIPSINVEST AS?

REDERIET STENERSEN AS
STENERSEN SHIPSINVEST AS
· NOK −126,000 profit

STENERSEN SHIPSINVEST AS has 5 registered shareholders:

All shareholders and roles →

Which companies does STENERSEN SHIPSINVEST AS own?

STENERSEN SHIPSINVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STENERSEN SHIPSINVEST AS

Who owns STENERSEN SHIPSINVEST AS?

REDERIET STENERSEN AS is the largest registered owner, with 70.1%.

Who is the general manager of STENERSEN SHIPSINVEST AS?

Sigve Stenersen is registered as general manager of STENERSEN SHIPSINVEST AS.

Where is STENERSEN SHIPSINVEST AS based?

STENERSEN SHIPSINVEST AS has its business address in Bergen.

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.