biztrac. BETA
COMPANY REGISTER PROFILE
998238943 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

TRIADEN KEBAB AS

Org. no. 998238943 Limited company (AS) Lørenskog Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 648,000
Equity NOK 73,000
Incorporated 2012
Share capital NOK 30,000

TRIADEN KEBAB AS is registered as a limited company in Lørenskog, Akershus with organisation number 998238943. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive gatekjøkken og fastfood restaurant samt hva som står i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 648,000 in operating profit.

Former names: LILLESTRØM KEBAB-GRILL OG PIZZA AS

Key figures · 2025

Revenue
NOK 4.7m
▼ −16 %
Operating profit
NOK 648,000
▲ +59 %
Equity
NOK 73,000
▲ +323 %
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
47.9%
Very good
Return on total assets
Solidity
6.4%
Weak
Equity as a share of total capital

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

Who owns TRIADEN KEBAB AS?

TRIADEN KEBAB AS
NOK 4.7m rev. · NOK 648,000 profit

TRIADEN KEBAB AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRIADEN KEBAB AS

Who owns TRIADEN KEBAB AS?

Ahmed Riaz is the largest registered owner, with 33.4%.

What is the revenue of TRIADEN KEBAB AS?

TRIADEN KEBAB AS had revenue of NOK 4.7m in 2025.

Who is the general manager of TRIADEN KEBAB AS?

Muhammad Rizwan is registered as general manager of TRIADEN KEBAB AS.

Where is TRIADEN KEBAB AS based?

TRIADEN KEBAB AS has its business address in Lørenskog.

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.