BIZTRAC BETA
Business and other management consultancy activities

MUTLE AS

Org. no. 996156788 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK −115,000
Incorporated 2010
Share capital NOK 120,000

Signals

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

MUTLE AS is registered as a limited company in Oslo, Oslo with organisation number 996156788. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2010. Registered share capital is NOK 120,000, divided into 120000 shares. The company's stated purpose is: “Selskapets formål er kjøp og salg av verdipapirer samt rådgiving og informasjonstjeneste innenfor områdene samfunnskontakt for bedrifter og internasjonal politikk og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2024

Operating profit
NOK −11,000
Equity
NOK −115,000

Financial health · 2024

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

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

Who owns MUTLE AS?

KRISTIN HETLE
MUTLE AS
· NOK −11,000 profit

MUTLE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MUTLE AS own?

MUTLE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MUTLE AS

Who owns MUTLE AS?

KRISTIN HETLE is the largest registered owner, with 50.0%.

Where is MUTLE AS based?

MUTLE AS has its business address in Oslo.

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.