BIZTRAC BETA
Restaurant activities

SOLI M INVEST AS

Org. no. 924720530 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 836,000
Operating profit NOK −593,000
Equity NOK −1.8m
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,8 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−593k kr).

SOLI M INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 924720530. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av restauranter og kafeer.”. The most recent filed accounts, for the 2024 financial year, show NOK 836,000 in revenue and NOK −593,000 in operating profit.

Key figures · 2024

Revenue
NOK 836,000
Operating profit
NOK −593,000
Equity
NOK −1.8m

Financial health · 2024

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
146.6%
Weak
Equity as a share of total capital

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

Who owns SOLI M INVEST AS?

SULIMAN MANSOUR ABU JAZAR
SOLI M INVEST AS
NOK 836,000 rev. · NOK −593,000 profit

SOLI M INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLI M INVEST AS

Who owns SOLI M INVEST AS?

SULIMAN MANSOUR ABU JAZAR is the largest registered owner, with 100.0%.

What is the revenue of SOLI M INVEST AS?

SOLI M INVEST AS had revenue of NOK 836,000 in 2024.

Who is the general manager of SOLI M INVEST AS?

Suliman Mansour Abu Jazar is registered as general manager of SOLI M INVEST AS.

Where is SOLI M INVEST AS based?

SOLI M INVEST 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.