BIZTRAC BETA
Restaurant activities

ZIJO AS

Org. no. 830000402 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 6.6m
Operating profit NOK −1.5m
Equity NOK −3.4m
Incorporated 2022
Employees 8
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,5 mill kr).

ZIJO AS is registered as a limited company in Oslo, Oslo with organisation number 830000402. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive restaurant og pizzeria - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.6m in revenue and NOK −1.5m in operating profit.

Key figures · 2024

Revenue
NOK 6.6m
Operating profit
NOK −1.5m
Equity
NOK −3.4m

Financial health · 2024

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

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

Who owns ZIJO AS?

ARIABOD AS
ZIJO AS
NOK 6.6m rev. · NOK −1.5m profit

ZIJO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ZIJO AS

Who owns ZIJO AS?

ARIABOD AS is the largest registered owner, with 80.0%.

What is the revenue of ZIJO AS?

ZIJO AS had revenue of NOK 6.6m in 2024.

Who is the general manager of ZIJO AS?

Zijad Harcevic is registered as general manager of ZIJO AS.

Where is ZIJO AS based?

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