BIZTRAC BETA
Restaurant activities

KEBAB ZONE AS

Org. no. 931871846 Limited company (AS) Fredrikstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 692,000
Operating profit NOK −134,000
Equity NOK −533,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−533k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−134k kr).

KEBAB ZONE AS is registered as a limited company in Fredrikstad, Østfold with organisation number 931871846. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift av gatekjøkken samt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 692,000 in revenue and NOK −134,000 in operating profit.

Key figures · 2025

Revenue
NOK 692,000
Operating profit
NOK −134,000
Equity
NOK −533,000

Financial health · 2025

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

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

Who owns KEBAB ZONE AS?

SAFIULLAH SAFI
KEBAB ZONE AS
NOK 692,000 rev. · NOK −134,000 profit

KEBAB ZONE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KEBAB ZONE AS

Who owns KEBAB ZONE AS?

SAFIULLAH SAFI is the largest registered owner, with 100.0%.

What is the revenue of KEBAB ZONE AS?

KEBAB ZONE AS had revenue of NOK 692,000 in 2025.

Who is the general manager of KEBAB ZONE AS?

Safiullah Safi is registered as general manager of KEBAB ZONE AS.

Where is KEBAB ZONE AS based?

KEBAB ZONE AS has its business address in Fredrikstad.

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.