BIZTRAC BETA
Business and other management consultancy activities

MOUN10 AS

Org. no. 923788743 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 621,000
Operating profit NOK −766,000
Equity NOK −2.5m
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,5 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−766k kr).

MOUN10 AS is registered as a limited company in Asker, Akershus with organisation number 923788743. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i aksjer og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 621,000 in revenue and NOK −766,000 in operating profit.

Key figures · 2025

Revenue
NOK 621,000
Operating profit
NOK −766,000
Equity
NOK −2.5m

Financial health · 2025

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

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

Who owns MOUN10 AS?

Christoffer Wang
MOUN10 AS
NOK 621,000 rev. · NOK −766,000 profit

MOUN10 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MOUN10 AS own?

MOUN10 AS holds stakes in 5 companies:

See the full ownership structure →

Group structure

MOUN10 AS er morselskap for 1 datterselskap:

Frequently asked questions about MOUN10 AS

Who owns MOUN10 AS?

Christoffer Wang is the largest registered owner, with 100.0%.

What is the revenue of MOUN10 AS?

MOUN10 AS had revenue of NOK 621,000 in 2025.

Where is MOUN10 AS based?

MOUN10 AS has its business address in Vettre.

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.