BIZTRAC BETA
COMPANY REGISTER PROFILE
919103981 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

CHARLIES KEBAB TORSHOV AS

Org. no. 919103981 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 465,000
Equity NOK 439,000
Incorporated 2017
Share capital NOK 30,000

CHARLIES KEBAB TORSHOV AS is registered as a limited company in Oslo, Oslo with organisation number 919103981. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Gatekjøkken, take away og alt annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 465,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 465,000
Equity
NOK 439,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns CHARLIES KEBAB TORSHOV AS?

ZAHID ABBAS
CHARLIES KEBAB TORSHOV AS
NOK 3.3m rev. · NOK 465,000 profit

CHARLIES KEBAB TORSHOV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHARLIES KEBAB TORSHOV AS

Who owns CHARLIES KEBAB TORSHOV AS?

ZAHID ABBAS is the largest registered owner, with 100.0%.

What is the revenue of CHARLIES KEBAB TORSHOV AS?

CHARLIES KEBAB TORSHOV AS had revenue of NOK 3.3m in 2025.

Who is the general manager of CHARLIES KEBAB TORSHOV AS?

Zahid Abbas is registered as general manager of CHARLIES KEBAB TORSHOV AS.

Where is CHARLIES KEBAB TORSHOV AS based?

CHARLIES KEBAB TORSHOV 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.