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

A-LI DRABANTEN AS

Org. no. 816565812 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK −267,000
Equity NOK 50,000
Incorporated 2016
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−267k kr).

A-LI DRABANTEN AS is registered as a limited company in Oslo, Oslo with organisation number 816565812. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2016. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Å drive restaurant med servering av mat og drikker , catering og import & eksport av matvarer virksomhet, samt kjøp & salg av aksjer og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −267,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK −267,000
Equity
NOK 50,000
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
0.65
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.5%
Weak
Equity as a share of total capital

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

Who owns A-LI DRABANTEN AS?

MOHSEN MATORY
A-LI DRABANTEN AS
NOK 2.5m rev. · NOK −267,000 profit

A-LI DRABANTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about A-LI DRABANTEN AS

Who owns A-LI DRABANTEN AS?

MOHSEN MATORY is the largest registered owner, with 100.0%.

What is the revenue of A-LI DRABANTEN AS?

A-LI DRABANTEN AS had revenue of NOK 2.5m in 2025.

Where is A-LI DRABANTEN AS based?

A-LI DRABANTEN 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.