BIZTRAC BETA
Freight ocean transport

STENSTRAUM SHIPPING AS

Org. no. 979678967 Limited company (AS) Bergen Incorporated 1998 Active
Ownership graph ↗
Operating profit NOK −114,000
Equity NOK 139.8m
Incorporated 1998
Share capital NOK 4.0m

Signals

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

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

Key figures · 2024

Operating profit
NOK −114,000
Equity
NOK 139.8m
Est. value
NOK 383.7m

Financial health · 2024

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

Who owns STENSTRAUM SHIPPING AS?

STENERSEN SHIPSINVEST AS
STENSTRAUM SHIPPING AS
· NOK −114,000 profit

STENSTRAUM SHIPPING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STENSTRAUM SHIPPING AS own?

STENSTRAUM SHIPPING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STENSTRAUM SHIPPING AS

Who owns STENSTRAUM SHIPPING AS?

STENERSEN SHIPSINVEST AS is the largest registered owner, with 55.0%.

Who is the general manager of STENSTRAUM SHIPPING AS?

Sigve Stenersen is registered as general manager of STENSTRAUM SHIPPING AS.

Where is STENSTRAUM SHIPPING AS based?

STENSTRAUM SHIPPING 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.