BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

MUCHOS INVESTOS AS

Org. no. 825136142 Limited company (AS) Ålesund Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 351,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

MUCHOS INVESTOS AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 825136142. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsbransjen: Aktiv og varig investering i aksjer og andre verdipapirer samt aktiv forvaltning av egne midler og investeringer i eiendom og andre liknende aktiva.”.

Key figures · 2024

Operating profit
NOK −5,000
Equity
NOK 351,000
Est. value
NOK 505,000

Financial health · 2024

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

Who owns MUCHOS INVESTOS AS?

JONAS INGEBRIGTSEN
MUCHOS INVESTOS AS
· NOK −5,000 profit

MUCHOS INVESTOS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MUCHOS INVESTOS AS own?

MUCHOS INVESTOS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MUCHOS INVESTOS AS

Who owns MUCHOS INVESTOS AS?

JONAS INGEBRIGTSEN is the largest registered owner, with 100.0%.

Who is the general manager of MUCHOS INVESTOS AS?

Jonas Ingebrigtsen is registered as general manager of MUCHOS INVESTOS AS.

Where is MUCHOS INVESTOS AS based?

MUCHOS INVESTOS 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.