BIZTRAC BETA
Manufacture of cordage, rope, twine and netting

MØRENOT HOLDING AS

Org. no. 919895950 Limited company (AS) Ålesund Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −2.4m
Equity NOK 802.7m
Incorporated 2017
Share capital NOK 7.9m

Signals

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

MØRENOT HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 919895950. The business is classified under manufacture of cordage, rope, twine and netting (NACE 13.940). The company was incorporated in 2017. Registered share capital is NOK 7.9m, divided into 721738 shares. The company's stated purpose is: “Investere, eie og selge eller på annet vis helt eller delvis realisere virksomhet og selskaper, herunder innenfor fisk, akvakultur, seismikk og offshore, og utvikling og investering i andre selskaper og alt som står i forbindelse med de forannevnte virksomheter.”.

Key figures · 2024

Operating profit
NOK −2.4m
Equity
NOK 802.7m
Est. value
NOK 439.1m

Financial health · 2024

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

Who owns MØRENOT HOLDING AS?

HAMPIDJAN HF
MØRENOT HOLDING AS
· NOK −2.4m profit

MØRENOT HOLDING AS has 10 registered shareholders:

All shareholders and roles →

Which companies does MØRENOT HOLDING AS own?

MØRENOT HOLDING AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about MØRENOT HOLDING AS

Who owns MØRENOT HOLDING AS?

HAMPIDJAN HF is the largest registered owner, with 47.8%.

Where is MØRENOT HOLDING AS based?

MØRENOT HOLDING AS has its business address in Ålesund.

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.