BIZTRAC BETA
Uoppgitt

MALOWI HOLDING AS

Org. no. 931944045 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 3,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

MALOWI HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 931944045. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 3,000
Est. value
NOK 4,000

Financial health · 2025

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

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

Who owns MALOWI HOLDING AS?

SEBASTIAN DANIEL EMIR ISHOW WIESE
MALOWI HOLDING AS
NOK 0 rev. · NOK −14,000 profit

MALOWI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MALOWI HOLDING AS own?

MALOWI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MALOWI HOLDING AS

Who owns MALOWI HOLDING AS?

SEBASTIAN DANIEL EMIR ISHOW WIESE is the largest registered owner, with 100.0%.

What is the revenue of MALOWI HOLDING AS?

MALOWI HOLDING AS had revenue of NOK 0 in 2025.

Where is MALOWI HOLDING AS based?

MALOWI HOLDING 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.