BIZTRAC BETA
COMPANY REGISTER PROFILE
924576332 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Freight ocean transport

STENSTRAUM AS

Org. no. 924576332 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −389,000
Equity NOK 2.3m
Incorporated 2020
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−389k kr).

STENSTRAUM AS is registered as a limited company in Bergen, Vestland with organisation number 924576332. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2020. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Eie og drift av skip samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −389,000
Equity
NOK 2.3m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns STENSTRAUM AS?

STENSTRAUM AS
· NOK −389,000 profit

STENSTRAUM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STENSTRAUM AS

Who owns STENSTRAUM AS?

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

Where is STENSTRAUM AS based?

STENSTRAUM AS has its business address in Bergen.

Property

Business address Edvard Griegs vei 1, 5059 Bergen
Cadastral unit 4601-159/1020/0/0
Building Annen kontorbygning · 1 unit

38 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.