BIZTRAC BETA
Uoppgitt

MANGO TREE AS

Org. no. 926187120 Limited company (AS) Kongsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 308,000
Incorporated 2020
Share capital NOK 43,000

Signals

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

MANGO TREE AS is registered as a limited company in Kongsberg, Buskerud with organisation number 926187120. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 43,000, divided into 2685 shares. The company's stated purpose is: “Eie, kjøpe og selge aksjer og andeler i andre selskap, samt konsulenttjenester, foredragsholder, skuespilleroppdrag m.m.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 308,000
Est. value
NOK 362,000

Financial health · 2024

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

Who owns MANGO TREE AS?

ELSE HAUG STORAAS
MANGO TREE AS
NOK 0 rev. · NOK −6,000 profit

MANGO TREE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MANGO TREE AS own?

MANGO TREE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MANGO TREE AS

Who owns MANGO TREE AS?

ELSE HAUG STORAAS is the largest registered owner, with 100.0%.

What is the revenue of MANGO TREE AS?

MANGO TREE AS had revenue of NOK 0 in 2024.

Who is the general manager of MANGO TREE AS?

Else Haug Storaas is registered as general manager of MANGO TREE AS.

Where is MANGO TREE AS based?

MANGO TREE AS has its business address in Kongsberg.

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.