BIZTRAC BETA
Freight ocean transport

MYKLEBUSTHAUG INVEST AS

Org. no. 989251856 Limited company (AS) Austrheim Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −128,000
Equity NOK 48.6m
Incorporated 2005
Share capital NOK 600,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−128k kr).

MYKLEBUSTHAUG INVEST AS is registered as a limited company in Austrheim, Vestland with organisation number 989251856. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2005. Registered share capital is NOK 600,000, divided into 400 shares. The company's stated purpose is: “Eie og forvalte aksjer, obligasjoner og andre verdipapirer, eie og forvalte eiendom, deltagelse i andre selskaper, utøvelse av rådgivnings og konsulentvirksomhet, samt hva som står i forbindelse hermed.”.

Key figures · 2024

Operating profit
NOK −128,000
Equity
NOK 48.6m
Est. value
NOK 78.7m

Financial health · 2024

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

Who owns MYKLEBUSTHAUG INVEST AS?

MIKKAL ÅGE MYKLEBUSTHAUG
MYKLEBUSTHAUG INVEST AS
· NOK −128,000 profit

MYKLEBUSTHAUG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MYKLEBUSTHAUG INVEST AS own?

MYKLEBUSTHAUG INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MYKLEBUSTHAUG INVEST AS

Who owns MYKLEBUSTHAUG INVEST AS?

MIKKAL ÅGE MYKLEBUSTHAUG is the largest registered owner, with 100.0%.

Who is the general manager of MYKLEBUSTHAUG INVEST AS?

Mikkal Åge Myklebusthaug is registered as general manager of MYKLEBUSTHAUG INVEST AS.

Where is MYKLEBUSTHAUG INVEST AS based?

MYKLEBUSTHAUG INVEST AS has its business address in Fonnes.

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.