biztrac. BETA
COMPANY REGISTER PROFILE
829513102 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Bankrupt UPDATED 03.10.2026
⚠MALIKSEN2 AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Restaurant activities

MALIKSEN2 AS

Org. no. 829513102 Limited company (AS) Oslo Incorporated 2022 Bankrupt
Revenue 2024 NOK 2.4m
Operating profit NOK −271,000
Equity NOK −1.1m
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.

MALIKSEN2 AS is registered as a limited company in Oslo, Oslo with organisation number 829513102. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av gatekjøkken.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK −271,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
▼ −23 %
Operating profit
NOK −271,000
▲ +69 %
Equity
NOK −1.1m
▲ +34 %

Financial health · 2024

Liquidity
-0.30
Not satisfactory
Current assets ÷ current liabilities
Profitability
-29.4%
Not satisfactory
Return on total assets
Solidity
-80.6%
Weak
Equity as a share of total capital

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

Who owns MALIKSEN2 AS?

MALIKSEN2 AS
NOK 2.4m rev. · NOK −271,000 profit

MALIKSEN2 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MALIKSEN2 AS

Who owns MALIKSEN2 AS?

Iftikhar Malik is the largest registered owner, with 75.0%.

What is the revenue of MALIKSEN2 AS?

MALIKSEN2 AS had revenue of NOK 2.4m in 2024.

Who is the general manager of MALIKSEN2 AS?

Younas Waqas is registered as general manager of MALIKSEN2 AS.

Where is MALIKSEN2 AS based?

MALIKSEN2 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.