BIZTRAC BETA
Freight ocean transport

STOLT-NIELSENS REDERI AS

Org. no. 920421938 Limited company (AS) Oslo Incorporated 1925 Active
Ownership graph ↗
Operating profit NOK −84,000
Equity NOK −3.0m
Incorporated 1925
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,0 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−84k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STOLT-NIELSENS REDERI AS is registered as a limited company in Oslo, Oslo with organisation number 920421938. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 1925. Registered share capital is NOK 100,000. The company's stated purpose is: “Omsetning av sild og fisk, skipsfart, formidling av befraktning, kjøp og salg av skip, assuranse agentur, finansiering, investering i faste eien- dommer samt deltagelse i andre selskaper av enhver art.”.

Key figures · 2024

Operating profit
NOK −84,000
Equity
NOK −3.0m

Financial health · 2024

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

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

Who owns STOLT-NIELSENS REDERI AS?

STOLT-NIELSEN NORWAY AS
STOLT-NIELSENS REDERI AS
· NOK −84,000 profit

STOLT-NIELSENS REDERI AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STOLT-NIELSENS REDERI AS er morselskap for 2 datterselskaper:

Frequently asked questions about STOLT-NIELSENS REDERI AS

Who owns STOLT-NIELSENS REDERI AS?

STOLT-NIELSEN NORWAY AS is the largest registered owner, with 100.0%.

Where is STOLT-NIELSENS REDERI AS based?

STOLT-NIELSENS REDERI AS has its business address in Oslo.

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.