BIZTRAC BETA
Wholesale of other machinery and equipment

STORD MOORING GROUP AS

Org. no. 929097815 Limited company (AS) Stord Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −140
Equity NOK −42,000
Incorporated 2022
Share capital NOK 280,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−42k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−140 kr).

STORD MOORING GROUP AS is registered as a limited company in Stord, Vestland with organisation number 929097815. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2022. Registered share capital is NOK 280,000, divided into 2800 shares. The company's stated purpose is: “Investering i andre selskap, utstyr, eiendom, og annen virksomhet som naturlig faller inn under dette.”.

Key figures · 2024

Operating profit
NOK −140
Equity
NOK −42,000

Financial health · 2024

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

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

Who owns STORD MOORING GROUP AS?

JAN INGE ISAKSEN
STORD MOORING GROUP AS
· NOK −140 profit

STORD MOORING GROUP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STORD MOORING GROUP AS own?

STORD MOORING GROUP AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STORD MOORING GROUP AS

Who owns STORD MOORING GROUP AS?

JAN INGE ISAKSEN is the largest registered owner, with 100.0%.

Who is the general manager of STORD MOORING GROUP AS?

Jan Inge Isaksen is registered as general manager of STORD MOORING GROUP AS.

Where is STORD MOORING GROUP AS based?

STORD MOORING GROUP AS has its business address in Stord.

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.