BIZTRAC BETA
Freight ocean transport

SCAN-SHIPPING NORWAY AS

Org. no. 990026688 Limited company (AS) Bærum Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −20,000
Equity NOK −162,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

SCAN-SHIPPING NORWAY AS is registered as a limited company in Bærum, Akershus with organisation number 990026688. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Representasjon og drift av skip, samt tilknyttede aktiviteter og investering i eierandeler i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −20,000
Equity
NOK −162,000

Financial health · 2024

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

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

Who owns SCAN-SHIPPING NORWAY AS?

SCANWAY SHIPPING AS
SCAN-SHIPPING NORWAY AS
· NOK −20,000 profit

SCAN-SHIPPING NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SCAN-SHIPPING NORWAY AS

Who owns SCAN-SHIPPING NORWAY AS?

SCANWAY SHIPPING AS is the largest registered owner, with 100.0%.

Who is the general manager of SCAN-SHIPPING NORWAY AS?

Stig Asbjørn Bore is registered as general manager of SCAN-SHIPPING NORWAY AS.

Where is SCAN-SHIPPING NORWAY AS based?

SCAN-SHIPPING NORWAY AS has its business address in Lysaker.

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.