BIZTRAC BETA
Uoppgitt

MUJO AS

Org. no. 933710610 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 59,000
Operating profit NOK 48,000
Equity NOK 61,000
Incorporated 2024
Share capital NOK 30,000

MUJO AS is registered as a limited company in Oslo, Oslo with organisation number 933710610. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet 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 foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 59,000 in revenue and NOK 48,000 in operating profit.

Key figures · 2025

Revenue
NOK 59,000
Operating profit
NOK 48,000
Equity
NOK 61,000
Est. value
NOK 170,000

Financial health · 2025

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

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

Who owns MUJO AS?

PETTER SØLAND
MUJO AS
NOK 59,000 rev. · NOK 48,000 profit

MUJO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MUJO AS own?

MUJO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MUJO AS

Who owns MUJO AS?

PETTER SØLAND is the largest registered owner, with 100.0%.

What is the revenue of MUJO AS?

MUJO AS had revenue of NOK 59,000 in 2025.

Who is the general manager of MUJO AS?

Petter Søland is registered as general manager of MUJO AS.

Where is MUJO AS based?

MUJO 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.